Verified:GitHub

docker-extend

Extend Docker environments with gitignored override files and apt-get tool installation.

Updated May 13, 2026

Search Tags:#development environment #docker #docker compose #container customization #apt-get install #deployment mode #gitignored overrides

Ready to run

npx skills add https://github.com/cliffthelin/AXiomEngine --skill docker-extend-cliffthelin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: docker-extend
Source: https://github.com/cliffthelin/AXiomEngine/tree/main/archon/.claude/skills/docker-extend
Command: npx skills add https://github.com/cliffthelin/AXiomEngine --skill docker-extend-cliffthelin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of customizing a Docker-based environment with your own tools without modifying or committing maintainer-controlled Dockerfiles and compose files.

Core Features & Use Cases

Context-aware setup (DEV_MODE vs DEPLOY_MODE): Detects whether you are building from the root docker-compose.yml (source build) or using deploy/docker-compose.yml (GHCR image), and applies the correct customization targets.
Gitignored user override pattern: Creates or uses Dockerfile.user and docker-compose.override.yml (or their deploy/ equivalents) so your personal changes stay private and out of git.
Interactive tool installation: Adds requested packages into the appropriate user Dockerfile via an apt-get install block, enabling lightweight environment personalization.

Quick Start

Tell the AI to set up Docker customization and install tools by running: install vim ripgrep jq using docker-extend.

Frequently Asked Questions about docker-extend

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I add personal packages to a Docker container without modifying maintainer files?▼

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.

Can I customize my Docker development environment with apt-get install without committing changes to git?▼

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.

Does Docker customization work for both source build development mode and GHCR image deployment mode?▼

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.

What is the best way to extend a Docker Compose setup with user-specific tools safely?▼

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.

Why do my Docker override files not overwrite existing configurations when setting up user customization?▼

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.

Do I need to manually rebuild Docker after adding user-specific tools to the override Dockerfile?▼

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.