메뉴
Guidance for authoring PeiDocker user_config.yml files. Use when Codex needs to create or modify PeiDocker YAML for stages, images, SSH, ports, proxy, APT, environment variables, storage, mounts, devices, or lifecycle custom hooks.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
New-user entrypoint and router for PeiDocker guidance. Use when Codex needs to orient a user who is new, unsure where to start, asking broad PeiDocker questions, or needing help choosing among project workflow, user_config.yml authoring, built-in utility scripts, and running configured projects.
Guidance for PeiDocker CLI project workflows. Use when Codex needs to install or verify pei-docker-cli, create projects, choose quick templates or build modes, run configure or remove, inspect generated project structure, or decide which generated project files are durable edit targets.
Guidance for operating a configured PeiDocker project. Use when Codex needs to build, run, stop, connect to, validate, troubleshoot, or clean up a PeiDocker project using Docker Compose, SSH, exec, GPU checks, or merged-build helper scripts.
Guidance for using PeiDocker built-in utility scripts. Use when Codex needs to choose installer or helper scripts, understand their parameters, place them in user_config.yml custom hooks, or reason about build-time versus runtime paths.
| name | pei-docker-user-config |
| description | Guidance for authoring PeiDocker user_config.yml files. Use when Codex needs to create or modify PeiDocker YAML for stages, images, SSH, ports, proxy, APT, environment variables, storage, mounts, devices, or lifecycle custom hooks. |
Use this skill for user_config.yml authoring. For CLI project creation use $pei-docker-cli-workflow; for built-in installer scripts use $pei-docker-utility-scripts; for running an already configured project use $pei-docker-run-project.
Before inventing YAML, consult the narrowest relevant source:
src/pei_docker/templates/config-template-full.ymlsrc/pei_docker/templates/quick/*.ymlsrc/pei_docker/examples/**/user_config.ymldocs/manual/concepts/*, docs/manual/guides/*openspec/specs/*/spec.md for env, ports, mounts, scripts, and installersPreserve user-owned values. Do not replace a whole config when a focused YAML edit is enough.
Read only the reference files needed for the user's task:
| Task | Reference |
|---|---|
| Stage selection, image base/output, devices | references/stage-image.md |
| SSH users, auth, keys, UID/GID | references/ssh-access.md |
stage_2.storage, mount, /soft, /hard | references/storage-and-mounts.md |
| Ports, proxy, APT mirrors, China/corporate network setup | references/networking-proxy-apt-ports.md |
${VAR} and {{VAR}} semantics | references/environment-variables.md |
| Custom lifecycle hooks and script placement | references/custom-hooks.md |
user_config.yml.pei-docker-cli configure when feasible.stage_1.ssh.stage_2.storage accepts only app, data, and workspace.mount entries need explicit absolute dst_path values.stage_2.image.base is omitted./soft/... do not exist during stage-2 on_build.{{...}} are limited to compose-emitted values and are incompatible with merged build.After meaningful edits, prefer:
pei-docker-cli configure -p <project-dir>
If validation fails, inspect the error and adjust user_config.yml or custom source scripts. Do not hand-edit generated wrappers as the durable fix.