> ## Documentation Index
> Fetch the complete documentation index at: https://docs.acusight.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Container management & logs

> Real container orchestration on every edge device — start, stop, inspect, stream logs, and open a console from the dashboard.

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](https://www.portainer.io/) Edge Agent that AcuSight provisions alongside its own agent; see [Edge agent](/hardware/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.

<Frame caption="Device overview — hardware, Docker version, and live counts across the device's stacks, containers, images, volumes, and networks.">
  <img src="https://mintcdn.com/brinqaiinc/7s4qAxCwrjuLPQeS/images/guides/operate/docker-containers.png?fit=max&auto=format&n=7s4qAxCwrjuLPQeS&q=85&s=19115b1a3b37928790dba9aea4ab2648" alt="Device info panel with CPU, memory, Docker version, and container, image, volume, and network counts" width="3315" height="1036" data-path="images/guides/operate/docker-containers.png" />
</Frame>

## 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.

<Frame caption="Container Management — every container on the device, with status, health, image, ports, and stack, plus quick actions on each row.">
  <img src="https://mintcdn.com/brinqaiinc/7s4qAxCwrjuLPQeS/images/guides/operate/container-management.png?fit=max&auto=format&n=7s4qAxCwrjuLPQeS&q=85&s=e6ed203558a8d6b5a54f266374feb611" alt="Container Management page listing the device's containers with statuses and quick actions" width="3339" height="1633" data-path="images/guides/operate/container-management.png" />
</Frame>

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.

<Frame caption="Container logs, streamed live from an edge device — with stdout/stderr filters, auto-refresh, and download.">
  <img src="https://mintcdn.com/brinqaiinc/7s4qAxCwrjuLPQeS/images/guides/operate/container-logs.png?fit=max&auto=format&n=7s4qAxCwrjuLPQeS&q=85&s=5bc9bfac36c9ca7a4d9dc523386ce0f0" alt="Container Details Logs tab streaming live logs with filter and download controls" width="3348" height="1858" data-path="images/guides/operate/container-logs.png" />
</Frame>

## 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.

<Frame caption="The Console tab — an interactive shell into a running container, straight from the dashboard.">
  <img src="https://mintcdn.com/brinqaiinc/7s4qAxCwrjuLPQeS/images/guides/operate/container-console.png?fit=max&auto=format&n=7s4qAxCwrjuLPQeS&q=85&s=453b66b21159a110f0ffad3b9067568b" alt="Container Details Console tab with command and user fields and a Connect button" width="3348" height="1858" data-path="images/guides/operate/container-console.png" />
</Frame>

## 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.

<Note>
  Container management rides the same **outbound-only** tunnel as everything else. The tunnel opens only when you actually view a device's containers, stacks, or logs, and closes after a few minutes of inactivity — nothing on the device stays reachable between sessions. See [Edge agent](/hardware/edge-agent#under-the-hood).
</Note>

## Next steps

<CardGroup cols={2}>
  <Card title="Device settings" icon="sliders" href="/guides/operate/device-settings">
    Configure a device's video sources, zones, analytics, and network.
  </Card>

  <Card title="Reliability" icon="shield-check" href="/guides/operate/reliability">
    What AcuSight runs for you, and what stays yours.
  </Card>
</CardGroup>
