1. 1. Summary

The antithesis workload image build fetches Python dependencies over the network in three unretried `RUN` layers — the pip/wheel upgrade, the pinned `uv` install, and the `uv sync`. Any transient network fault in one of them aborts the docker build, which propagates up through `docker_cluster_image_builder.py` and system-fails the Evergreen task.

1. 1. Changes

• Wrap `pip install --upgrade pip wheel`, `pip install uv==...`, and `python -m venv && uv sync` in the existing `retry_apt.sh` helper (6 attempts, exponential backoff).
• Move `RUN rm /usr/local/bin/retry_apt.sh` from line 45 to after the last use. It previously deleted the helper before the python-deps stage, so those layers could not have used it.

No new files — `retry_apt.sh` is already copied into this build context by `docker_cluster_image_builder.py`, and its signature (`"description" command [args...]`) is already generic despite the apt-flavored name.

`mongo_binaries/Dockerfile` has no python dependency stage and needs no equivalent change.