Docker / Compose, Swarm & Production Security
Explain a Compose service omitted by inactive profiles
A defined service may be excluded from ordinary startup because its profile is not active. Inspect declared profile names and deployment intent.
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 compose config --profilesRead the result
With supported Compose v2, this lists profile names in the resolved model. It does not prove which profiles a previous invocation activated.
Resolve and verify
Compare the real deployment command and approved environment with service profile assignments. Enable only intended services through the reviewed workflow and verify dependencies.
Before changing production
Do not activate every debug or administration profile in production merely to make a missing service appear.