linuxmirrors-docker
为 Linux 主机规划 LinuxMirrors Docker Engine 安装、Docker CE 软件源更换和 Docker Registry Mirror 配置，覆盖版本选择、已有安装、仅换 Registry、多镜像地址、daemon.json 合并、服务验证与回滚。用户提到 docker.sh、DockerInstallation.sh、Docker 拉取加速或 --only-registry 时使用；普通系统软件源更换不使用本技能。
- Installs
- 48
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/full-stack-skills/devops-skills --skill linuxmirrors-docker- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads linuxmirrors-docker automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
LinuxMirrors Docker 安装与换源
Quick Start
先区分三条路径：全新安装 Docker Engine、替换 Docker CE 软件包仓库、仅配置 Registry Mirror。三者影响面不同，不要把“安装源”和“镜像拉取加速”混写。
可直接使用：
- “为 Rocky Linux 9 规划 Docker Engine 安装和验证，先不要执行。”
- “Docker 已安装，只用 LinuxMirrors 更换 Registry Mirror。”
- “安全合并多个 registry-mirrors 到现有 daemon.json，并给回滚步骤。”
只读确认 Docker 状态：
docker version 2>/dev/null || true
检查当前 Mirror，不修改配置：
docker info 2>/dev/null | sed -n '/Registry Mirrors/,+5p'
检查 Compose V2：
docker compose version 2>/dev/null || true
什么时候使用
当用户要安装 Docker Engine、更换 Docker CE 软件包仓库、配置 Registry Mirror 或排查 docker.sh/--only-registry 时使用。普通系统软件源、Docker Desktop、containerd/Kubernetes 全局镜像配置不适用。
适用用户
- 新手：先区分全新安装、CE 仓库和 Registry 三种模式。
- 运维人员：重点保护 repo、daemon.json、服务状态与容器数据。
- 平台工程师：使用显式版本、固定脚本提交、批次验证和回滚门禁。
前置条件
必须知道发行版、版本、架构、Docker 是否已安装、init 系统、现有 daemon.json 和维护授权。
使用方式
Step 1：预检
读取预检清单，确认发行版、版本、架构、root、Docker 状态、init 系统和现有配置。
Step 2：选路径
全新安装/修复 CE 仓库/--only-registry 三选一，参考模式差异。
Step 3：定参数
从参数参考选择源、Registry、版本及语言参数。
Step 4：保护现场
备份 /etc/docker/daemon.json 和 Docker CE repo 文件，记录当前 Docker 版本与服务状态。
Step 5：先确认再执行
展示影响面；默认不关闭防火墙，不在未知生产机直接运行。
Step 6：验证
检查 repo、docker version、服务状态、docker info Registry Mirrors 与实际拉取。
Step 7：回滚
按回滚指南恢复 JSON/repo 备份并重启或恢复原服务状态。
能力边界与不适用场景
✅ 擅长处理
- Debian 系和 Red Hat 系 Linux 上的 Docker Engine 安装及 Docker CE 仓库换源规划。
- 已安装 Docker 的
--only-registry、单个/多个 Registry Mirror 和daemon.json合并。 - 指定版本、内网源、服务验证、失败排查和配置回滚。
⚠️ 需要条件
- 实际安装需要 root、受支持发行版、网络、维护窗口和包管理器可用。
- 指定
--designated-version需要先查询仓库实际提供的完整版本。 - 现有
daemon.json含代理、日志驱动、私有仓库等配置时必须做 JSON 级合并而非覆盖。
❌ 超出范围（给替代方案）
- Docker Desktop、Windows 或 macOS → 使用 Docker Desktop 官方设置与企业策略。
- Rootless Docker、无兼容包管理器的独立发行版 → 参考 Docker 官方二进制或 rootless 文档。
- Kubernetes/containerd 全局镜像配置 → 使用对应运行时与集群配置流程，不能只改 Docker。
资料路由
- 完整选项：读参数参考。
- 支持范围：读兼容性。
- 三种工作模式：读模式差异。
- 主脚本与 Lite：读脚本选择。
- 运行前：读预检清单。
- JSON 安全合并：读daemon.json 指南。
- 恢复配置：读回滚指南。
- 报错排查：读故障排查。
安全与隐私
本技能不收集或上传用户数据，不要求主机密码、SSH 私钥或 Registry 凭据。先审查远程脚本再运行。默认保留防火墙，只有用户明确授权并理解暴露面时才讨论 --close-firewall true。不要覆盖未知的 daemon.json，不要把私有 Registry 凭据写入示例。
Rules
- 禁止混淆 Docker CE 软件源和 Registry Mirror。
- 禁止臆造安装版本、仓库路径、镜像地址或验证结果。
- 默认不关闭防火墙，不覆盖现有 daemon.json，不删除容器数据。
- 服务启动失败先验证 JSON 和日志，再决定恢复备份。
信息不足时
先按“Docker 已安装、只更换 Registry、systemd、保留现有 daemon.json、不关闭防火墙、只生成方案”给出安全示例。请补充：发行版与版本、架构、Docker 是否已安装、目标是 CE 软件源还是 Registry、init 系统、现有 daemon.json、是否有私有仓库或代理。
验证清单
- 是否明确选择安装、CE 仓库或仅 Registry 路径？
- 参数是否存在于当前
DockerInstallation.sh --help？ daemon.json是否先通过jq/JSON 解析校验并备份？- 是否保持防火墙默认不变？
- 是否同时验证服务状态、
docker info和实际拉取？
Gotchas
- Docker CE 软件源决定软件包下载，Registry Mirror 决定镜像拉取，二者不可互换。
--only-registry检测不到 Docker Engine 时会退出，不能当作安装命令。- 直接重写
daemon.json会丢失日志、代理、data-root 等现有配置；必须合并。 - Registry Mirror 可访问不代表 Docker CE 软件仓库可访问，反之亦然。
--close-firewall true影响主机安全边界，不得作为默认“安装优化”。- 指定版本只写
28.0.0仍可能受发行版包版本格式影响，先查询仓库列表。
FAQ
Q1：只想加速拉镜像怎么办？ Docker 已安装时使用 --only-registry，并通过 --source-registry 指定一个或多个地址。
Q2：多个地址怎么写？ 使用英文逗号分隔，并验证每个地址；顺序代表尝试优先级而非自动测速。
Q3：Compose 需要单独安装吗？ 当前脚本集成 Docker Compose V2 插件，使用 docker compose，不要默认依赖旧的 docker-compose。
Q4：如何确认 Mirror 生效？ docker info 查看 Registry Mirrors，再拉取公开小镜像并观察错误与耗时。
Q5：可以覆盖 daemon.json 吗？ 只有确认文件不存在或内容可全部替换时；默认应解析、合并、校验和备份。
Q6：脚本支持所有 Linux 吗？ Docker 脚本主要面向 Debian 系和 Red Hat 系及衍生版；独立发行版要改用官方安装方式。
FAQ
What does the linuxmirrors-docker skill do?
为 Linux 主机规划 LinuxMirrors Docker Engine 安装、Docker CE 软件源更换和 Docker Registry Mirror 配置，覆盖版本选择、已有安装、仅换 Registry、多镜像地址、daemon.json 合并、服务验证与回滚。用户提到 docker.sh、DockerInstallation.sh、Docker 拉取加速或 --only-registry 时使用；普通系统软件源更换不使用本技能。
How do I install linuxmirrors-docker?
Run npx skills add https://github.com/full-stack-skills/devops-skills --skill linuxmirrors-docker in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/linuxmirrors-docker/ (personal) or .claude/skills/linuxmirrors-docker/ (project).
Which AI agents can use linuxmirrors-docker?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is linuxmirrors-docker safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains linuxmirrors-docker?
It is published by full-stack-skills in full-stack-skills/devops-skills. It has 48 recorded installs.
More from full-stack-skills/devops-skills
kubernetes
full-stack-skills/devops-skills
Open the skill to read its SKILL.md instructions.
github-actions
full-stack-skills/devops-skills
Open the skill to read its SKILL.md instructions.
gitlab-ci
full-stack-skills/devops-skills
Open the skill to read its SKILL.md instructions.
terraform
full-stack-skills/devops-skills
Open the skill to read its SKILL.md instructions.
ansible
full-stack-skills/devops-skills
Open the skill to read its SKILL.md instructions.
cloudformation
full-stack-skills/devops-skills
Open the skill to read its SKILL.md instructions.
Popular devops & cloud skills
microsoft-foundry
microsoft/azure-skills
Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end. USE FOR: foundry, azd ai agent, azd provision/deploy, hosted agent scaffold/develop/run/deploy/troubleshoot, prompt agent create, managed harness agent create, GitHub Copilot harness agent, create agent, update agent, add tool to agent, invoke agent, agent insights, evaluate agent, batch eval, continuous eval, continuous monitoring, agent CI/CD, optimize prompt, improve prompt, optimize agent instructions, Agent Optimizer scaffold, dataset curation from traces, deploy model, model fine-tuning (SFT/DPO/RFT), Foundry project, RBAC, role assignment, permissions, quota, capacity, region, deployment failure, AI Services, create Foundry resource, knowledge index, customize deployment, onboard, availability, training-data, grader, distillation, large file upload. DO NOT USE FOR: Azure Functions, App Service, general Azure deploy (use azure-deploy), general Azure prep (use azure
azure-diagnostics
microsoft/azure-skills
Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, lock renewal during long-running processing, service bus dead letter.
azure-prepare
microsoft/azure-skills
Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.
azure-ai
microsoft/azure-skills
Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.
azure-deploy
microsoft/azure-skills
Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.
azure-validate
microsoft/azure-skills
Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity permissions, and prerequisites before deploying. WHEN: validate my app, check deployment readiness, run preflight checks, verify configuration, check if ready to deploy, validate azure.yaml, validate Bicep, test before deploying, troubleshoot deployment errors, validate Azure Functions, validate function app, validate serverless deployment, verify RBAC roles, check role assignments, review managed identity permissions, what-if analysis, validate Container Apps deployment.