podman-pod-logs(1)
π podman-pod-logs β bestie edition π
okay so real quick, this is podman-pod-logs from the General Commands Manual, section 1. it's a whole vibe, let's get into it π«Ά
β¨ NAME β¨
podman-pod-logs β pull up the logs for a pod that's got one or more containers in it π
πΈ SYNOPSIS πΈ
podman pod logs [options] pod
like. that's it. that's the whole entrance. π
π¦ DESCRIPTION π¦
okay so podman pod logs batch-retrieves whatever logs are present with all the containers of a pod. all of them. at once. it's giving group project but everyone actually showed up.
and if you're not tryna read every single container's receipts, pod logs can be filtered by container name or ID using the -c or --container flag. yesss, pick your fave. π
Note: a long-runningpodman pod logcommand with a-for--followoption needs to be reinvoked if a new container gets added to the pod dynamically. otherwise, logs of newly added containers are not visible in the log stream. like, the stream literally doesn't know about the new girl. so if you added a container mid-follow, you gotta re-run it. no cap. π
π OPTIONS π
--colorβ outputs the containers with different colors in the log. rainbow moment, very slay. π--container,-cβ by default,podman pod logsretrieves logs for all the containers available within the pod, differentiated by the fieldcontainer. but sometimes you're in your main character era and you only want the log stream for one particular container of a pod. for those cases, use-clikepodman pod logs -c ctrNameorID podname. π―--follow,-fβ follow log output. default isfalse.
Note: when following a pod that gets removed bypodman pod rmor removed on exit (podman run --rm ...), there's a chance that the log file is removed beforepodman pod logsreads the final content. yeah. it's a race condition bestie, sometimes the file just dips early π
--latest,-lβ instead of providing the pod name or ID, use the last created pod.
Note: the last started pod can be from other users of Podman on the host machine. π (this option is not available with the remote Podman client, including Mac and Windows (excluding WSL2) machines)
--names,-nβ output the container names instead of the container IDs in the log. so much more readable, we love a name drop. β¨--since=TIMESTAMPβ show logs since TIMESTAMP. the--sinceoption can be Unix timestamps, date formatted timestamps, or Go duration strings (e.g.10m,1h30m) computed relative to the client machine's time. supported formats for date formatted time stamps includeRFC3339Nano,RFC3339,2006-01-02T15:04:05,2006-01-02T15:04:05.999999999,2006-01-02Z07:00, and2006-01-02. so many options and every single one is valid π--tail=LINESβ output the specified number of LINES at the end of the logs. LINES must be an integer. defaults to-1, which prints all lines. (yes,-1means everything, it's giving "no limits".)--timestamps,-tβ show timestamps in the log outputs. the default isfalse. β°--until=TIMESTAMPβ show logs until TIMESTAMP. the--untiloption can be Unix timestamps, date formatted timestamps, or Go duration strings (e.g.10m,1h30m) computed relative to the client machine's time. supported formats for date formatted time stamps includeRFC3339Nano,RFC3339,2006-01-02T15:04:05,2006-01-02T15:04:05.999999999,2006-01-02Z07:00, and2006-01-02. same formats as--since, iconic symmetry. πͺ
π EXAMPLE π
to view a pod's logs:
podman pod logs -t podIdorName
to view logs of a specific container on the pod:
podman pod logs -c ctrIdOrName podIdOrName
to view all pod logs:
podman pod logs -t --since 0 myserver-pod-1
to view a pod's logs since a certain time:
podman pod logs -t --since 2017-08-07T10:10:09.055837383-04:00 myserver-pod-1
to view a pod's logs generated in the last 10 minutes:
podman pod logs --since 10m myserver-pod-1
to view a pod's logs until 30 minutes ago:
podman pod logs --until 30m myserver-pod-1
go off bestie, run every single one of these, they all ate π₯
π§ SEE ALSO π§
podman(1), podman-pod(1), podman-pod-rm(1), podman-logs(1)
like yeah, go read those too, they're the supporting cast and they understood the assignment π
and that's the whole page!! brought to you by the General Commands Manual, podman-pod-logs(1), section 1 β mwah, take care of her, she's doing her best ππΈπ¦β¨ππ«Ά
π¦ where this page comes from
- arch rolling: podman-docker 6.1.4-1 Β· Apache-2.0
- fedora 43: podman-docker 5:5.6.2-1.fc43 Β· Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND ISC AND MIT AND MPL-2.0
- fedora 43: podman-docker 5:5.8.4-1.fc43
- fedora 43: podman-docker 5:5.8.8-1.fc43
- fedora 43: podman-docker 5:5.8.9-1.fc43 Β· Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND ISC AND MIT AND MPL-2.0
- fedora 44: podman-docker 5:5.8.1-1.fc44 Β· Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND ISC AND MIT AND MPL-2.0
- fedora 44: podman-docker 5:5.8.7-1.fc44
- fedora 44: podman-docker 5:5.8.9-1.fc44 Β· Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND ISC AND MIT AND MPL-2.0
- ubuntu resolute: podman-docker 5.7.0+ds2-3build1 Β· Apache-2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms