Update to Cloud Environment
Snapshot Nov 14, 2026 · 00:16 UTC · version 0.2.1
Package or technical metadata updated
Package or technical metadata updated
Observed in package metadata. These changes alone do not establish a new customer-facing feature.
Up to 3 plugins free · no card required.
All fields and original values.
These are saved file metadata. Open a changed file to read its text edits.
Package file
Nov 7, 2026 · 06:11 UTC
43c1edfd46ed50089691d1c28f21956d9c75dddde78bfa8f7c0993cce9bf737b
Nov 14, 2026 · 00:16 UTC
3e6b43af9be41a4fdb6529dd0dacb6b9f728ca68df6f8c823ce37ae84b9224fe
Package file
Nov 7, 2026 · 06:11 UTC
7482
Nov 14, 2026 · 00:16 UTC
2717
Package file
Nov 7, 2026 · 06:11 UTC
Not present
Nov 14, 2026 · 00:16 UTC
{"sha256":"a6bb372c3d5d7e3937fdb9ed58182dc8a1766363ab066e5dfd3885779a18b8d8","size":2185}
Package file
Nov 7, 2026 · 06:11 UTC
ec96d051bb55af47524272b4444c84009e8cc0f111571eeeb2b5ebf4eb38b21b
Nov 14, 2026 · 00:16 UTC
9bd1d89e13f20e650ae7d47afa3bee49dc98f4cff38480a359f6b30aff985f53
Compare saved observations
Download comparison JSONChanged files
Choose a file to see its text changes. Binary or large files show metadata only.
SKILL.md →
references/docker.md
− removed · + added
--- before +++ after @@ -1,79 +1,20 @@ -# Docker in a managed cloud environment +# Build and run Docker containers -This environment is a Docker container and supports Docker in Docker. The -platform starts the Docker daemon and configures Docker's default proxy settings. - -When Docker is needed, check the managed daemon explicitly. Clear endpoint, -context, and TLS selectors for this command so inherited settings or a saved -`currentContext` cannot redirect the check to another daemon: +Fresh customer environments on the default image use rootless Docker. Restored, custom, or internal images can differ. As the task user, probe the managed socket even if a saved context or inherited settings point to a different daemon. ```sh env -u DOCKER_HOST -u DOCKER_CONTEXT -u DOCKER_TLS \ -u DOCKER_TLS_VERIFY -u DOCKER_CERT_PATH \ - docker --host=unix:///var/run/docker.sock info + docker --host=unix:///var/run/docker.sock info --format '{{.ServerVersion}}' ``` -Keep `DOCKER_CONFIG` and registry credentials unchanged. If this local-socket -check fails, check whether `dockerd` is running and check your user ID with -`id -u`. Starting or restarting the daemon requires root (UID 0). A non-root -task user has socket access but no permission -to start or restart the daemon; no privileged startup helper is provided. In -that case, report the diagnostic and request environment recovery. - -As root, you may start a stopped daemon using the inherited `HTTP_PROXY`, -`HTTPS_PROXY`, and `NO_PROXY` environment variables and the configured system CA -trust. Docker's client proxy defaults alone do not configure daemon egress. -Keep the existing storage driver, data directory, and socket group. For the -provided daemon defaults, the following command refuses to start a second daemon -and removes the stale pidfile only after confirming no `dockerd` process is -running. It creates a fresh runtime directory so restored containerd PID and -socket files cannot interfere with startup; Docker's persistent data stays in -its existing location: +Use the same local endpoint for builds and runs. If the shell targets another daemon, use the same `env -u` options and explicit `--host` for those commands too. Preserve `DOCKER_CONFIG` and registry credentials. -```sh -( -set -e -if pgrep -x dockerd >/dev/null; then - echo 'dockerd is already running; inspect it before restarting.' >&2 - exit 1 -else - # pgrep returns 1 for no matches; other errors must not trigger recovery. - [ "$?" -eq 1 ] || exit 1 -fi -install -d -m 0700 /run/codex-docker -rm -f /run/codex-docker/dockerd.pid -docker_exec_root="$(mktemp -d /run/codex-docker/exec-XXXXXX)" -docker_socket_gid="$(stat -c %g /var/run/docker.sock 2>/dev/null || id -g)" -nohup /usr/local/bin/dind /usr/local/bin/dockerd \ - --host=unix:///var/run/docker.sock \ - --pidfile=/run/codex-docker/dockerd.pid \ - --exec-root="$docker_exec_root" \ - --storage-driver="${CAAS_DIND_STORAGE_DRIVER:-vfs}" \ - --group="$docker_socket_gid" \ - >/run/codex-docker/dockerd.log 2>&1 </dev/null & -) -``` +## Build with HTTPS + +Docker's client supplies the session proxy to builds and new containers. Keep its configured address. The executor's `proxy` hostname, certificate store, and package registry mirror settings do not automatically carry into an inner container. If a dependency installs on the host but fails in a build, check which registry the build actually contacts. -Repeat the local-socket health check above until it succeeds before Docker work; -inspect the daemon log if it does not become ready within 60 seconds. To restart -an unhealthy daemon as root, inspect its log and existing arguments, stop that -specific process and wait for it to exit. Start it with a fresh runtime directory -as above, preserving its data directory, storage driver, socket group, and proxy -environment. -Restarting interrupts running containers. Do not launch a competing daemon or -change storage drivers to recover it. - -## Builds that use the network - -Internet access goes through a proxy. Docker's client defaults -supply the proxy to builds and new containers. Inner containers do not inherit -the outer container's certificate stores or its `proxy` hosts entry. Preserve -the platform's reachable proxy address and existing Docker configuration, -including registry credentials. - -If a tool in a Dockerfile needs HTTPS access, mount the provided CA during the -build and configure that tool's trust settings. Keep TLS verification enabled. -For Node/npm, adapt the relevant dependency-installing step: +Try the project's normal build and trust settings first. If HTTPS needs the session CA, use the project's existing build option or mount the CA as a BuildKit secret in each step that needs it. For a session-only adjustment, adapt a temporary copy of the Dockerfile and preserve the original build context and ignore rules. For example, an npm build can use this step. ```dockerfile # syntax=docker/dockerfile:1 @@ -81,69 +22,36 @@ WORKDIR /app COPY package.json package-lock.json ./ RUN --mount=type=secret,id=proxy_ca,required=true \ - NODE_EXTRA_CA_CERTS=/run/secrets/proxy_ca \ - npm ci --strict-ssl=true + NODE_EXTRA_CA_CERTS=/run/secrets/proxy_ca npm ci --strict-ssl=true COPY . . ``` -Pass the certificate in the build command: +Set `session_dockerfile` to the path of the adapted copy and build with the project's usual context (here, `.`). ```sh -docker build --secret id=proxy_ca,src="$CODEX_PROXY_CERT" -t app . +docker build -f "$session_dockerfile" --secret id=proxy_ca,src="$CODEX_PROXY_CERT" -t app . ``` -The mount exists only for that `RUN`. Repeat it in every networked step and -every stage that needs it. The CA is public, but the BuildKit secret mount keeps -this session-specific file out of image layers. Do not `COPY` it into the image. - -There is no universal CA environment variable. For Python Requests use -`REQUESTS_CA_BUNDLE`, for pip use `PIP_CERT`, and for uv or clients that honor it -use `SSL_CERT_FILE`. These settings may replace the normal roots instead of -extending them. Mount the outer system bundle from -`/etc/ssl/certs/ca-certificates.crt` as a separate build secret when a combined -bundle is appropriate. Set the inner tool's variable to its mounted path. -For Java, Gradle, Bazel, or OS-managed trust, adapt that tool's trust store and -ensure session certificates and generated stores do not remain in image layers. -Do not fix a certificate error with `--insecure`, `strict-ssl=false`, or by -disabling certificate verification. - -Buildx and Compose builds need the same secret supplied through their build -configuration. Proxy defaults do not supply the CA automatically. - -## Running containers - -New containers receive Docker's default proxy environment. Give a process that -needs HTTPS a read-only CA mount and its appropriate trust setting. For this -example, use Node.js 22.21 or newer; `NODE_USE_ENV_PROXY=1` makes `fetch()` use -the inherited proxy settings: +For Buildx or Compose, supply the secret through the build configuration. Keep the session CA out of image layers. For clients that replace their normal trust roots, mount the executor's combined bundle (`/etc/ssl/certs/ca-certificates.crt`) and point the client at its mounted path. Requests uses `REQUESTS_CA_BUNDLE`, pip uses `PIP_CERT`, and uv supports `SSL_CERT_FILE`. For Java or other tools with a separate trust store, configure that store for the step. Keep TLS verification enabled. + +## Run with HTTPS + +Bind-mount the CA read-only and point the process at the mount. This example uses Node 22.21 or newer, where `NODE_USE_ENV_PROXY=1` makes `fetch` use the proxy. ```sh docker run --rm \ --mount "type=bind,src=$CODEX_PROXY_CERT,dst=/run/proxy-ca.pem,readonly" \ - -e NODE_EXTRA_CA_CERTS=/run/proxy-ca.pem \ - -e NODE_USE_ENV_PROXY=1 \ + -e NODE_EXTRA_CA_CERTS=/run/proxy-ca.pem -e NODE_USE_ENV_PROXY=1 \ node:22-bookworm-slim \ node -e 'fetch("https://registry.npmjs.org").then(r => { if (!r.ok) process.exit(1); })' ``` -Use a combined CA bundle for clients whose setting replaces default roots. -Existing containers retain the environment they were created with; recreate -them if their saved proxy address belongs to a prior session. - -## Diagnose the failing layer - -- The local-socket health check fails: inspect the daemon/socket setup before - changing a Dockerfile. -- Pull fails: inspect registry authentication, the configured network policy, - and the exact registry error. Proxy build arguments do not configure daemon - egress. Registry rate limits may require a registry account. -- A build step cannot connect: check the inherited proxy and destination policy. - Do not replace the configured proxy address with the outer-only `proxy` hostname. -- A build or runtime process reports a certificate error: supply the CA to that - particular step/process, including later build stages, then retry with TLS - verification enabled. - -Network access remains subject to the environment's configured policy. A blocked -destination requires an approved configuration change. Do not bypass the proxy -or use host networking to work around policy. Do not print Docker config, -registry credentials, or the full process environment while diagnosing failures. +Recreate containers that still have a previous session's proxy address. + +## Diagnose the failing step + +- **Local socket.** Check whether Docker is installed, the socket exists, and the task user can access it (`id`, `ls -l /var/run/docker.sock`). Cloud can finish provisioning even if Docker is disabled or its startup failed. For a rootless image, check the managed socket at `/run/codex-docker/docker.sock` too. If only that socket works, use it explicitly and report the broken standard socket. +- **FUSE mount.** Privileged Kata guests can expose `/dev/fuse`. Check for the character device and the image’s mount helper (for example, `fusermount3`). A nested container also needs an authorized device mapping and mount permissions. If the device or permissions are missing, report the failing layer. +- **Daemon recovery.** If Docker is disabled, use a project-supported alternative if it satisfies the task. Start a stopped daemon only if the task already runs as root, the active environment allows rootful Docker, and the image documents a startup procedure. Check for a running `dockerd` first. Starting a second daemon or restarting a live one can disrupt containers. Preserve its storage driver, data directory, socket group, proxy environment, and system CA trust. Use a fresh execution directory after a restore, then repeat the socket probe. For a rootless or unconfirmed profile, or a non-root task user, report the failed probe and request recovery through the managed environment. +- **Image pull.** Check the registry error, authentication, rate limit, and destination policy. The daemon uses its own proxy and trust settings for pulls. Build arguments affect only build steps. +- **Build or container request.** Check the exact failing step's proxy and CA mount. For a policy denial, follow [Environment changes](environment-changes.md). Keep traffic on the configured proxy. Report the error without printing Docker configuration, registry credentials, or the full process environment.
Full technical diff · 13 changed fields
changed /files/SKILL.md/sha256
"43c1edfd46ed50089691d1c28f21956d9c75dddde78bfa8f7c0993cce9bf737b"
"3e6b43af9be41a4fdb6529dd0dacb6b9f728ca68df6f8c823ce37ae84b9224fe"
changed /files/SKILL.md/size
7482
2717
added /files/references~1diagnostics.md
Field was absent
{
"sha256": "a6bb372c3d5d7e3937fdb9ed58182dc8a1766363ab066e5dfd3885779a18b8d8",
"size": 2185
}changed /files/references~1docker.md/sha256
"ec96d051bb55af47524272b4444c84009e8cc0f111571eeeb2b5ebf4eb38b21b"
"9bd1d89e13f20e650ae7d47afa3bee49dc98f4cff38480a359f6b30aff985f53"
changed /files/references~1docker.md/size
6846
4876
added /files/references~1environment-changes.md
Field was absent
{
"sha256": "9031adb8fc4bc76168adb0c9d502b3b444e4d4ea222a5b89b281088f4b42039e",
"size": 2907
}changed /files/references~1networking.md/sha256
"349d5b56dfff6f3973852941af2b59b2576d9461d851d167fa78da7f5a7dfd49"
"ba6e3cfd91b79daf90430c1e35fcda9ff2c00ebf0066d6b6d0bddbaf3f2f2328"
changed /files/references~1networking.md/size
6117
5521
changed /files/references~1packages.md/sha256
"7079ae62edd61083e1f448b845c7d6120e26e98882e918844403695f53ece6c9"
"44cb76bfcde73f0392483f47211e736a55f5b4b6cf892db40790be673cc348d7"
changed /files/references~1packages.md/size
1751
1500
added /files/references~1repositories.md
Field was absent
{
"sha256": "9de3c0553f84cad0fd177775e5cfc66efa1ccee38ba551783cef57acab3db1f1",
"size": 1644
}changed /files/references~1vpn.md/sha256
"29e446165d393c5179bb3619f652b9b1e2e2e93723146cd51f0a2b7ad56d6bef"
"aa1afd30d1293fd5efa48e27103c430e46f4ffee215c7e17f8179359dc891a45"
changed /files/references~1vpn.md/size
11165
6758
Full snapshot data
{
"files": {
"SKILL.md": {
"sha256": "3e6b43af9be41a4fdb6529dd0dacb6b9f728ca68df6f8c823ce37ae84b9224fe",
"size": 2717
},
"references/diagnostics.md": {
"sha256": "a6bb372c3d5d7e3937fdb9ed58182dc8a1766363ab066e5dfd3885779a18b8d8",
"size": 2185
},
"references/docker.md": {
"sha256": "9bd1d89e13f20e650ae7d47afa3bee49dc98f4cff38480a359f6b30aff985f53",
"size": 4876
},
"references/environment-changes.md": {
"sha256": "9031adb8fc4bc76168adb0c9d502b3b444e4d4ea222a5b89b281088f4b42039e",
"size": 2907
},
"references/networking.md": {
"sha256": "ba6e3cfd91b79daf90430c1e35fcda9ff2c00ebf0066d6b6d0bddbaf3f2f2328",
"size": 5521
},
"references/packages.md": {
"sha256": "44cb76bfcde73f0392483f47211e736a55f5b4b6cf892db40790be673cc348d7",
"size": 1500
},
"references/repositories.md": {
"sha256": "9de3c0553f84cad0fd177775e5cfc66efa1ccee38ba551783cef57acab3db1f1",
"size": 1644
},
"references/vpn.md": {
"sha256": "aa1afd30d1293fd5efa48e27103c430e46f4ffee215c7e17f8179359dc891a45",
"size": 6758
},
"scripts/ensure-socat.sh": {
"sha256": "5d978e9230c4363dc84e2169e0385efaff2f1b5259da8fb15ed57924fdcd13f0",
"size": 2962
}
}
}SHA-256 of public snapshot: 2b4ab2c623d83912c640d4c04265cc45b082cd34a9af2220b4da16f08e19f686