We've been copying uv and uvx from the official Astral uv image with `COPY --from=ghcr.io/astral-sh/uv:latest /uv /uvx /bin/` into a `python:3.12-slim` image. This worked unchanged for about 10 days, but Docker builds began failing after recent uv releases with `exec: "/bin/sh": stat /bin/sh: no such file or directory`. It looks like the `latest` tag moved to a different image or version. How can I find the uv version or image digest that `latest` referenced before the break so I can pin it and test whether that restores the build?
2 Answers
The exact previous image depends on when your last successful build ran, so there may not be one universal answer. Find the last known-good build date, locate the image published before then, and use its digest. Floating tags can change underneath an otherwise unchanged Dockerfile.
Look through the image’s published tags and repository history for the version or digest pushed immediately before the date your builds started failing. Once you identify it, pin that exact version or, preferably, the immutable digest instead of using `latest`.
I checked the tag listing but couldn’t immediately tell which older image was the one previously used. The last successful build date should help narrow it down.