docker-extend

Extend Docker environments with user-selected packages while preserving maintainer files.

Updated May 21, 2026
One-click install
npx skills add https://github.com/sunzcdev/archon-dev-team --skill docker-extend-sunzcdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docker-extend
Source: https://github.com/sunzcdev/archon-dev-team/tree/main/.claude/skills/docker-extend
Command: npx skills add https://github.com/sunzcdev/archon-dev-team --skill docker-extend-sunzcdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents you from having to fork or manually maintain Docker changes every time you want extra tools inside your container.

Core Features & Use Cases

  • Personal Docker customization: Creates and edits user-specific Dockerfile and compose override files that are designed to be gitignored.
  • Dev vs deploy awareness: Detects whether you are building from source (repo-root compose) or running a GHCR/deploy setup and applies changes in the correct directory.
  • Tool installation updates: Adds or uncomments the apt-get install section for requested packages, including a safe cleanup of apt lists.

Quick Start

Ask the AI to extend your Docker image with tools like "vim ripgrep jq" so it can create the needed user override files and update your Dockerfile.user accordingly.

Frequently Asked Questions about docker-extend

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

FAQPage Schema
How do I install additional packages in a Docker container without modifying the project's Dockerfile?

To install packages without modifying the project Dockerfile, you can use a gitignored Dockerfile.user and a docker-compose.override.yml. This approach adds user-selected tools via apt-get while keeping maintainer files unchanged.

Can I add development tools like vim and ripgrep to a Docker deployment without forking the repository?

Yes, you can add development tools like vim and ripgrep without forking by creating user-specific Docker override files. This isolates your personal customizations from the main repository, preventing merge conflicts.

What is the best way to customize a Docker Compose setup for local development without affecting the source code?

The best way to customize a Docker Compose setup without affecting source code is using a docker-compose.override.yml file. This local override injects personalized configurations and package installations while keeping the original compose file intact.

Does Docker customization work for both source builds and GHCR deployment environments?

Docker customization works for both source builds and GHCR deployments by detecting the active compose context. It automatically applies user package installations to the correct directory, whether it is a root-based dev compose or a deploy setup.

How do I update the apt-get install section in a Docker user override file?

To update the apt-get install section in a Docker user override, you specify the requested packages in the Dockerfile.user. The system adds or uncomments the apt-get install command and includes a safe cleanup of apt lists.

Why should I use a gitignored configuration for Docker container personalization?

You should use a gitignored configuration for Docker container personalization to maintain a clean project history. This prevents personal tools and settings from being committed to the shared repository, avoiding conflicts with upstream changes.