docker-extend

To add personal packages to a Docker container without modifying maintainer files, use gitignored override Dockerfiles and compose files. This pattern copies missing .example override files without overwriting existing ones, then edits the Dockerfile.user apt-get install block to inject your requested tools safely.

Yes, you can customize your Docker development environment using gitignored override files. By applying a Dockerfile.user and docker-compose.override.yml, your apt-get install customizations remain private and completely out of git version control.

Docker customization works for both source build development mode and GHCR image deployment mode. The process detects whether you are building from the root docker-compose.yml or using deploy/docker-compose.yml, then applies the correct override targets for your specific scenario.

The best way to extend a Docker Compose setup safely is using gitignored override files. This approach detects your current build mode, copies missing .example override files without overwriting, and edits the correct Dockerfile.user apt-get install block for your requested tools.

Docker override files do not overwrite existing configurations because the setup process explicitly copies missing .example override files without overwriting. This ensures your current personal customizations remain intact while safely applying new user-specific tool installations.

You need to manually rebuild Docker after adding user-specific tools because the process provides the appropriate rebuild commands without auto-execution. This ensures you maintain full control over when the container rebuilds with your new apt-get install packages.