Follow-on from #85. That issue removed the Docker Hub account from the deployment path, but the builds themselves still fetch their base images from Docker Hub:
docker/Dockerfile.back FROM python:3.11-slim
docker/Dockerfile.ngrok FROM alpine:latest
These are anonymous pulls of public images, so no account is involved and nothing is broken today. Two reasons to move them anyway:
- Docker Hub applies rate limits to anonymous pulls, counted per source address. CI runners share egress addresses, so a build can start failing for reasons unrelated to any change in this repository.
- The ngrok image is built on the deployment host during every deploy, so a rate limit or outage there fails the deploy rather than just a build.
Both images are Docker Official Images and are mirrored by AWS at public.ecr.aws/docker/library/, which serves the same content without an account and with far more generous anonymous limits. ghcr.io/astral-sh/uv is already off Docker Hub.
Switching both would leave nothing in the build chain pointing at Docker Hub.
Follow-on from #85. That issue removed the Docker Hub account from the deployment path, but the builds themselves still fetch their base images from Docker Hub:
These are anonymous pulls of public images, so no account is involved and nothing is broken today. Two reasons to move them anyway:
Both images are Docker Official Images and are mirrored by AWS at
public.ecr.aws/docker/library/, which serves the same content without an account and with far more generous anonymous limits.ghcr.io/astral-sh/uvis already off Docker Hub.Switching both would leave nothing in the build chain pointing at Docker Hub.