Container management & logs

Each AcuSight device runs its workload as Docker containers, and the dashboard gives you real orchestration over them — not a read-only status page. You can start, stop, inspect, and read the logs of what’s running on any device, all remotely. This is powered by an embedded Portainer Edge Agent that AcuSight provisions alongside its own agent; see Edge agent for how that channel works.

​

The device at a glance

Opening a device’s containers starts with the device itself: its address, hardware (CPU, memory, OS/architecture), Docker version, and a live count of its stacks, containers, images, volumes, and networks — including how many containers are running, stopped, healthy, or unhealthy.

​

Containers

Container Management lists everything running on the device — each container’s status and uptime, health, image, published ports, IP address, and the stack it belongs to. Quick actions on every row let you work a container without opening it. Open a container for the full Container Details view, organized into tabs — Overview, Logs, Inspect, Stats, Console, Attach, and Networks — with actions to start, stop, and restart it.

​

Logs

The Logs tab streams a container’s output straight from the device — the first place to look when something on a device isn’t behaving. You can filter stdout/stderr, toggle timestamps and word wrap, set how many lines to fetch, auto-refresh on an interval, and download the log for offline digging.

​

Console

Need to poke around inside a running container? The Console tab gives you an interactive shell — pick the command (such as /bin/sh) and optionally the user, then Connect. It’s the equivalent of docker exec into the container, from the browser.

​

Stacks

Devices that run a multi-container workload manage it as a stack (a Docker Compose deployment). From a stack you can:

• View and edit its Compose definition and environment variables.
• Update to redeploy the stack with your changes.
• Stop and start the whole stack at once.

​

Images, volumes, and networks

The same views cover the rest of a device’s Docker resources — images, volumes, and networks — so you can manage a device end to end without a shell on the box.

​

Next steps