Containerizing an application with Docker for production

We need to package our web application with Docker and get it ready to run in production. Right now the project only runs on developer laptops, and every deployment turns into manual environment setup, so versions drift apart and the same bugs keep coming back. We want clean images for the backend, the frontend and the background workers, with their builds described in Dockerfiles using multi-stage builds so the final image stays small and does not carry build tooling. All services must be wired into one composition: the database, the cache, the message queue and the application itself should come up with a single command and survive a restart without losing data. That calls for named volumes, careful handling of environment variables and secrets, and health checks for the containers. The release procedure matters just as much: building, tagging, pushing to a registry and updating the server with no downtime. Please describe how to set up logging, monitoring and rollback to the previous version. Real production experience is required, and a solid grasp of networking and resource limits is a big plus.