**Bug: `egress-firewall.sh` path mismatch in python-runner Dockerfile**

[ian-aibymlsg]

Description
When running pnpm run update:clawix -- --pull after the latest update, the build fails because the python-runner Dockerfile references egress-firewall.sh at the build context root, but the file is located at infra/docker/egress-firewall.sh instead of infra/docker/python-runner/egress-firewall.sh.

Error

ERROR: failed to build: failed to solve: failed to compute cache key: failed to calculate checksum of ref ...: "/egress-firewall.sh": not found

Steps to reproduce

1. Run pnpm run update:clawix -- --pull on the latest main
2. Build fails at the python-runner Docker image step

Workaround
Manually copy the file to the expected location:

cp infra/docker/egress-firewall.sh infra/docker/python-runner/

Expected behaviour
The file should either be placed in infra/docker/python-runner/ in the repo, or the Dockerfile COPY path should be updated to reference the correct location.

Environment

• macOS (Mac mini)
• Docker Desktop
• Clawix commit: 5c5b194

[jasonli0226]

Thanks for the report! I tried to reproduce this on current main (86fafd7) and the build succeeds. A couple of things don't line up, so I'd like to confirm your setup before we dig further.

The python-runner image is built with infra/docker as the build context, not the python-runner/ subdirectory:

docker build -t clawix-python-runner:latest -f infra/docker/python-runner/Dockerfile infra/docker

(see scripts/update.mjs, scripts/install.mjs, scripts/setup-dev.sh). With that context, COPY egress-firewall.sh correctly resolves to infra/docker/egress-firewall.sh, which exists. The COPY python-runner/pip.conf line in the same Dockerfile also relies on this parent context. egress-firewall.sh is intentionally shared between python-runner and shell-net-runner, so it lives one level up.

Two things about the commit you listed (5c5b194):

• It is not the latest commit — current main is 86fafd7. Please git pull and re-run pnpm run update:clawix -- --pull to make sure you're on the latest.
• It also predates the egress-firewall entrypoint — at 5c5b194 the Dockerfile has no egress-firewall.sh reference and the file doesn't exist in the tree. That feature landed later (feat: human-in-the-loop tool approvals + network-capable shell #52), so the error you're seeing couldn't have originated from that exact commit.

Could you share:

1. The exact command you ran and its full output (especially the docker build ... line)?
2. git rev-parse HEAD in your checkout?

My current guess is the build was invoked with infra/docker/python-runner as the context instead of infra/docker — that would produce exactly this error.

[jasonli0226]

Correction to my earlier guess — the specific error text points somewhere else.

The python-runner Dockerfile copies pip.conf before egress-firewall.sh:

COPY python-runner/pip.conf /etc/pip.conf          # line 14
COPY egress-firewall.sh /usr/local/bin/egress-firewall.sh   # line 32

If the build context were wrong (e.g. infra/docker/python-runner instead of infra/docker), the first COPY would fail on pip.conf, and you'd see a pip.conf-not-found error — not egress-firewall.sh. Since your error is specifically "/egress-firewall.sh": not found, that line 14 pip.conf COPY must have succeeded, which means your build context was correct but the egress-firewall.sh file was missing from your checkout.

egress-firewall.sh is git-tracked and not ignored, so a clean checkout has it. The most likely explanation is an incomplete/inconsistent checkout — the newer Dockerfile (which references egress-firewall.sh) is present, but the file itself wasn't pulled. This also fits the commit you cited (5c5b194), which predates the file entirely.

Could you run, in your checkout, and paste the output:

git status
git rev-parse HEAD
ls -l infra/docker/egress-firewall.sh

If that ls shows the file missing, a clean git pull --ff-only (or git checkout -- infra/docker/egress-firewall.sh) should resolve it. We're also adding a preflight check to the build scripts so an incomplete checkout fails with a clear message instead of the cryptic Docker checksum error.