Docker-Compose Logs Path
/var/lib/docker/containers/<container_id>/<container_id>-json.log
DreamCoder
/var/lib/docker/containers/<container_id>/<container_id>-json.logDebugging Docker Issues with Container Logs
Docker has a dedicated API for working with logs. But, keep in mind, it will only work if you use the json-file log driver. I strongly recommend not changing the log driver! Let’s start debugging.
First of all, to list all running containers, use the docker ps command.
docker ps
Then, with the docker logs command you can list the logs for a particular container.
docker logs <container_id>
Most of the time you’ll end up tailing these logs in real time, or checking the last few logs lines.
Using the --follow or -f flag will tail -f (follow) the Docker container logs:
docker logs <container_id> -f
The --tail flag will show the last number of log lines you specify:
docker logs <container_id> --tail N
The -t or --timestamp flag will show the timestamps of the log lines:
docker logs <container_id> -t
The --details flag will show extra details about the log lines:
docker logs <container_id> --details
But what if you only want to see specific logs? Luckily, grep works with Docker logs as well.
docker logs <container_id> | grep pattern
This command will only show errors:
docker logs <container_id> | grep -i error