fix: container now copies managed python into runtime

Author: coretl

.devcontainer/devcontainer.json

@@ -8,8 +8,6 @@
     "remoteEnv": {
         // Allow X11 apps to run inside the container
         "DISPLAY": "${localEnv:DISPLAY}",
-        // We put venv on a different volume to cache so have to copy
-        "UV_LINK_MODE": "copy",
         // Do the equivalent of "activate" the venv so we don't have to "uv run" everything
         "PATH": "/workspaces/${localWorkspaceFolderBasename}/.venv/bin:${containerEnv:PATH}"
     },

template/Dockerfile.jinja

@@ -16,6 +16,9 @@ WORKDIR /app
 COPY . /app
 RUN chmod o+wrX .
 
+# Tell uv sync to install python in a known location so we can copy it out later
+ENV UV_PYTHON_INSTALL_DIR=/python
+
 # Sync the project without its dev dependencies
 RUN --mount=type=cache,target=/root/.cache/uv \
     uv sync --locked --no-editable --no-dev
@@ -50,6 +53,9 @@ FROM ubuntu:noble AS runtime
 #     some-library \
 #     && apt-get dist-clean
 
+# Copy the python installation from the build stage
+COPY --from=build /python /python
+
 # Copy the environment, but not the source code
 COPY --from=build /app/.venv /app/.venv
 ENV PATH=/app/.venv/bin:$PATH