Description

Fixes: prefix-dev/pixi-docker#134

This changes the way when we tell uv to load the built-in certificates.

How Has This Been Tested?

Test reproduction:

FROM ghcr.io/prefix-dev/pixi:0.63.1
COPY pyproject.toml ./
RUN pixi install

With a pyproject.toml containing a PyPI dependency (e.g., polars).

E.g

# pyproject.toml
[project]
dependencies = []
name = "tmp.s5BuMt3dvU"
requires-python = ">= 3.11"
version = "0.1.0"

[build-system]
build-backend = "hatchling.build"
requires = ["hatchling"]

[tool.pixi.workspace]
channels = ["conda-forge"]
platforms = ["osx-arm64", "linux-aarch64", "linux-64"]

[tool.pixi.pypi-dependencies]
polars = "*"

Verified this by: Built pixi from this branch inside a Docker container and confirmed pixi install now succeeds without certificate errors. Like this

# Build stage - compile pixi from source
FROM rust:1.86 AS builder
WORKDIR /build
COPY pixi-src/ .
RUN cargo build -p pixi

# Runtime stage
FROM ghcr.io/prefix-dev/pixi:0.63.1
COPY --from=builder /build/target/debug/pixi /usr/local/bin/pixi
COPY pyproject.toml ./
# COPY pixi.lock ./
RUN pixi install

This means pixi-src needs to be available :)

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas