oc Logs Examples¶
Introduction¶
oc logs reads container logs from pods, deployments, builds, and previous crashed containers. Use selectors and --previous when troubleshooting restarts.
When You Need This Command¶
Use this command when you need to inspect, change, or verify OpenShift resources from the terminal without relying on the web console.
Syntax¶
oc <command> <resource> [name] -n <project>
Practical Examples¶
oc logs deployment/web -n app
oc logs deployment/web -c web -n app --tail=100
oc logs pod/web-7c9d7f6f8b-jx4mk -n app --previous
oc logs -f deployment/web -n app
Example output:
2026-05-30T10:12:31Z INFO server started on :8080
2026-05-30T10:12:34Z INFO readiness check passed
Verification¶
oc get events -n app --sort-by=.lastTimestamp
oc get pods -n app -o wide
Common Mistakes¶
- Looking only at the final error and ignoring events.
- Checking the wrong project with oc.
- Changing several objects at once before confirming the current state.
Production Notes¶
Run read-only commands first, check the active project, and prefer declarative manifests for repeatable changes.
Quick Checklist¶
- Confirm the active project.
- Inspect the exact object named in the error.
- Read recent events.
- Apply one focused fix.
- Verify status after the change.
Related Guides¶
Summary¶
oc Logs Examples is most useful when paired with verification. Check the project, run the command against the intended object, and confirm the resulting OpenShift state.