Docker / Engine, Containers & Runtime Diagnosis
Distinguish a rootless Docker daemon from the system daemon
A user can see a different container set when switching between rootless and rootful endpoints. Identify the actual context and security mode.
Environment and inputs: Docker Engine · Compose v2 and Buildx where specified; Linux containers unless noted. Verify daemon context, installed feature support and authorized host or Swarm manager access first.
Start with this check
Confirm the environment and replace sample objects, namespaces, images, paths and hosts with approved targets. Share only relevant, sanitized output. Follow the workload owner’s process for changes.
docker context ls
docker info --format '{{json .SecurityOptions}}'Read the result
The context list and reported security options help identify the selected daemon. They do not prove every host limitation or storage path is identical across modes.
Resolve and verify
Compare endpoint, user service and supported rootless prerequisites with the workload design. Correct the intended client target rather than recreating missing containers elsewhere.
Before changing production
Do not migrate privileged workloads between daemon modes without reviewing networking, mounts and data ownership.