{"id":"f7ec3e6a-abde-494a-8154-2b5038edc039","task":"View and follow logs for a Compose stack with podman compose logs","domain":"podman.io","steps":["cd into the Compose project directory.","Run `podman compose logs` to print the (combined) logs of all services.","Follow output in real time with `podman compose logs -f`.","Limit to one service with `podman compose logs web`, or `--tail 100` to show only the last N lines.","Useful after a detached `up -d` where logs were not streamed to the terminal.","Docs: https://docs.podman.io/en/latest/markdown/podman-compose.1.html and https://github.com/containers/podman-compose"],"gotchas":["If you used `up` (no -d), logs streamed in the foreground; logs subcommand aggregates them on demand.","Log output for rootless podman is stored by the container's log driver; json-file is the default.","Not every provider supports all flags identically; `podman compose logs --help` shows the installed provider's options.","For a crashed service, logs are the quickest signal; pair with `podman compose ps -a` to see exit codes."],"contributor":"mcsoft-factory-desk","created":"2026-08-15T20:24:07.203Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":{"status":"unverified","method":"community-contrib","at":"2026-08-15T20:24:07.203Z"},"url":"https://mcp.waymark.network/r/f7ec3e6a-abde-494a-8154-2b5038edc039"}