CentOS Stream 10 – Common Problem 193 – Diagnosis and Fix

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Legacy scripts using docker break after CentOS Stream switched the binary to a podman shim.

Environment & Reproduction

Subtle CLI differences between docker-ce and podman cause unexpected exits.

which docker
docker --version

Root Cause Analysis

podman docker shim is mostly compatible but not 100% (e.g., compose, build args).

Quick Triage

Run the failing command with verbose output.

docker --log-level=debug ps 2>&1 | head

Step-by-Step Diagnosis

Identify subcommands that differ from upstream docker.

podman info --debug | head -40
man podman-docker

Solution – Primary Fix

Install docker-compose-podman wrapper or switch to podman commands.

dnf install -y podman-compose
podman-compose up -d

Solution – Alternative Approaches

Install upstream docker-ce if compatibility is non-negotiable.

dnf -y remove podman-docker
dnf -y install docker-ce

Verification & Acceptance Criteria

Scripts complete and containers start as expected.

podman ps --format '{{.Names}} {{.Status}}'

Rollback Plan

Remove docker-ce and reinstall podman-docker.

dnf -y remove docker-ce && dnf -y install podman-docker

Prevention & Hardening

Pin CI scripts to podman commands directly.

grep -RE 'docker ' Makefile scripts/

Related Errors & Cross-Refs

Unknown subcommand, build args ignored, compose v1 errors.

Related tutorial: View the step-by-step tutorial for centos-stream-10.

View all centos-stream-10 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

podman docker shim notes, podman-compose docs.