要查看Docker容器日志，主要使用docker logs命令。1. 使用docker logs [容器名或ID]可直接查看日志；2. 添加-f參數(shù)可實時追蹤日志輸出；3. 通過--timestamps或-t可顯示時間戳；4. 使用--since和--until可按時間范圍過濾日志；5. 若容器無shell，仍可通過docker logs訪問stdout/stderr日志，或掛載卷以訪問自定義日志文件；6. 可通過docker inspect檢查容器使用的日志驅(qū)動，若非默認(rèn)JSON-file驅(qū)動，則需查閱對應(yīng)外部系統(tǒng)如syslog、Fluentd等獲取日志。

To view the logs of a Docker container, you primarily use the docker logs command. It gives you real-time insight into what’s happening inside a running container, which is especially useful for troubleshooting or monitoring behavior.

Check Logs Using docker logs

The most direct way to see logs from a container is with the docker logs command followed by the container name or ID. For example:

docker logs my_container

If you want to follow the log output in real time (like tailing a file), add the -f flag:

docker logs -f my_container

You can also include timestamps with the --timestamps or -t option:

docker logs -t my_container

This helps when you're debugging timing issues or correlating events across systems.

One helpful trick: if your container restarts often or has multiple instances, make sure to double-check the container ID or name using docker ps before viewing logs.

View Logs for a Specific Time Range

Sometimes you don’t need all logs — just those within a certain period. You can filter logs by time using the --since and --until options.

For example, to get logs from the past 10 minutes:

docker logs --since "10m" my_container

Or if you want logs between two specific timestamps:

docker logs --since "2023-10-01T10:00:00" --until "2023-10-01T10:15:00" my_container

This feature is handy when debugging a known issue window without wading through irrelevant log lines.

Access Logs When No Shell Is Available

Some containers are minimal and don’t have tools like bash or even sh. In these cases, you can't exec into the container to check log files directly. But that’s okay — because Docker captures stdout and stderr by default, you can still use docker logs as described above.

If your app writes custom log files inside the container (e.g., /var/log/app.log), and you can't access them via docker logs, you might consider mounting a volume during container startup so logs are written to a directory on the host machine. That way, you can read them directly from your host system without needing shell access.

Log Drivers and External Logging

Docker supports different logging drivers, such as syslog, journald, or JSON-file (the default). If your environment uses a centralized logging system, your containers may be configured to send logs elsewhere.

To check what logging driver a container is using:

docker inspect my_container | grep LogPath

If it's not using the default JSON-file driver, you may need to look at external services like Fluentd, Logstash, or cloud-based solutions (e.g., AWS CloudWatch) to retrieve logs.

Configuring the right logging driver depends on your infrastructure setup, but for local development, sticking with the default usually works fine.

That’s how you can access Docker container logs depending on your needs. Whether it’s checking recent output, filtering by time, or dealing with headless containers, there’s a method that fits. Just remember to verify container names and understand where your logs are being sent — especially in production environments.

以上是如何查看Docker容器的日誌？的詳細(xì)內(nèi)容。更多資訊請關(guān)注PHP中文網(wǎng)其他相關(guān)文章！