A transit-ticketing team packs a web API, a sidecar cron job, and a local database into one container so they can “share localhost.” What Docker design problem does that create?
Select an answer to reveal the explanation.
Short Explanation
One container, one main process—like one employee, one job description. Cramming API, cron, and database together means you cannot restart or scale them apart.
Full Explanation
Docker’s unit of deployment is a single main process (plus its children). Combining a web server, cron, and database in one container so they share localhost recreates a mini-monolith: independent restart, scale, and health checks become impossible. That is the Docker counterpart of independent deployability, not an OCIR or networking rule.