Error when building docker image with version v0.10.2

General
1

I’m building the Docker image using the v0.10.2 tag from the repository, but I encountered the following error during the build process:

E: Unable to locate package python3.12-dev
E: Couldn’t find any package by glob ‘python3.12-dev’
E: Couldn’t find any package by regex ‘python3.12-dev’
E: Unable to locate package python3.12-venv
E: Couldn’t find any package by glob ‘python3.12-venv’
E: Couldn’t find any package by regex ‘python3.12-venv’

I noticed that the Dockerfile was recently updated in a newer commit ([Build/CI] Revert back to Ubuntu 20.04, install python 3.12 with uv (… · nktduong/vllm-secure@27edd2a · GitHub), and when I build the image from the latest version, it works without any issues.
It seems that this change fixed the problem — but I’m not entirely sure why the modification was necessary.

Could you please explain what caused this issue with python3.12 in the earlier version, and whether it’s still possible to build the image from scratch using the older v0.10.2 tag?

Thank you!

2

The error occurs because the v0.10.2 Dockerfile used Ubuntu 22.04 as the base image, which does not provide python3.12-dev and python3.12-venv in its default repositories. The recent commit you referenced reverted the base image to Ubuntu 20.04 and switched to installing Python 3.12 using uv, which bypasses the missing package issue and allows the build to succeed. Thus, the modification was necessary to ensure Python 3.12 could be installed reliably in the Docker build context (commit details).

If you want to build from scratch using the older v0.10.2 tag, you would need to either (1) manually add a PPA or alternative source for Python 3.12 on Ubuntu 22.04 (which is not recommended for reproducibility), or (2) backport the Dockerfile changes from the newer commit to your v0.10.2 build. The root cause is the lack of official python3.12 packages in Ubuntu 22.04’s default repositories at the time (commit details).

Would you like a step-by-step guide to backport the fix or further details on the Dockerfile changes?

Sources:

Hint: Mention @RunLLM in the post for followups.