Docker

Combine apt-get update and install in a single Dockerfile RUN layer to prevent caching issues where stale package lists cause failed installs. This ensures package lists remain synchronized with the packages being installed during image building.

Docker containers get killed by the OOM killer when they exceed allocated memory limits. You can resolve runtime stability issues by configuring proper memory constraints and monitoring resource usage to prevent processes from consuming excessive host memory.

Named volumes are explicitly defined and managed by Docker, persisting across container recreations, while anonymous volumes are created automatically and often abandoned. Proper volume management prevents host permission issues and unintended data loss during container lifecycle changes.

Avoid using ENV or COPY for Docker secrets to prevent security vulnerabilities. Instead, use runtime secret injection methods to ensure sensitive data is not persisted in image layers, mitigating risks of unauthorized access to credentials.

Debug stopped Docker containers by inspecting logs and checking exit codes to determine the failure cause. You can inspect dead containers to review their state and runtime history before removing them from the system.

Clean up dangling images and build cache using Docker pruning commands to manage disk resources. Regular pruning of stopped containers and stale build cache prevents disk bloat and maintains deployment efficiency across your environment.