docker-extend

To add personal tools without modifying maintainer files, you can create a user-specific Dockerfile.user and docker-compose.override.yml. These files are automatically gitignored to keep your local Docker customization isolated from the core project.

The best way to extend a Dockerfile locally is by using a Dockerfile.user file. This approach detects your dev or deploy context and applies your personal tooling configurations while keeping the maintainer's original Dockerfile clean and unaltered.

Yes, you can use docker-compose.override.yml to install local development tools. The override file allows you to inject personal configurations and tools into your Docker containers locally, ensuring the changes remain gitignored and do not affect the shared project.

If example templates are missing, the personalization process automatically copies the necessary example files into your project. You can then edit these files to add requested tools like vim or ripgrep and run a final rebuild command to apply changes.

Docker personalization works in both root and deploy contexts by automatically detecting the current environment. It adjusts the file locations for your Dockerfile.user and docker-compose.override.yml accordingly to ensure proper local tooling integration.

You should not edit the main Dockerfile directly because it modifies maintainer files and risks committing local tools to the shared repository. Using a gitignored Dockerfile.user ensures the core images remain clean and your personal configurations stay local.