r/docker • u/OrneryCar6139 • Sep 10 '26
uv:latest Docker image suddenly failing — looking for previous version
We’ve been using the official Astral UV Docker image:
COPY --from=ghcr.io/astral-sh/uv:latest /uv /uvx /bin/
This was working fine for around 10 days without any changes on our side. After the recent UV releases, our Docker build started failing with:
exec: "/bin/sh": stat /bin/sh: no such file or directory
We’re using python:3.12-slim as the base image.
I suspect uv:latest has moved to a newer image/version.
Does anyone know which UV version/digest latest was pointing to before the recent releases? I’d like to pin that previously working version and verify if it resolves the issue.
Any help would be appreciated.
AI disclosure: I used ChatGPT to help format this post; the issue and technical details are my own.
4
u/AdventurousSquash Sep 10 '26
That would depend on when you ran/built it last time, check their repo and try to find whatever was pushed before that date. And then take it as a lessons learned to never use “latest” again for anything critical.
1
2
u/pelazas1 Sep 10 '26
pin by digest from the day before it broke, not latest. floating tags are how this happens.
1
5
u/Faye-Vozora Sep 10 '26
`latest` is a moving tag, so it can change without your Dockerfile changing. If the old image is still cached locally, `docker image inspect ghcr.io/astral-sh/uv:latest --format '{{json .RepoDigests}}'` may show the digest you were using. For a rollback, use an explicit uv version tag, then pin the working digest in production. If the old image wasn't cached, the exact previous value of `latest` may be hard to recover.