Skip to content

Read Docker container status and logs safely

Collect a small diagnostic sample without exposing secrets or changing containers.

Protect your data firstKeep a current off-server backup before reinstalling, updating, changing firewall rules, or running an application installer.
On this page

Inspect the containers

With an authorized Docker account, run:

docker ps -a
docker stats --no-stream
docker logs --tail 80 --since 15m CONTAINER_NAME

Replace CONTAINER_NAME with the intended container name. These inspect status, one resource sample, and recent output; they do not restart or remove containers. Docker permissions are powerful, so do not grant daemon access merely to read logs.

Interpret the result

A running container may still have an unhealthy app. Check startup errors, listening ports, and the configured health check. Some logging drivers do not supply every log through this command.

Before sharing

Logs can contain tokens, database URLs, personal data, or request headers. Share only the relevant redacted lines and their timestamp. Avoid unbounded log output, full environment dumps, or publishing Docker's control socket.

Docker log reference.

Was this not enough?Include the service number, exact error, and time of the problem. Never send a password or private key.
Contact support