Chainguard Container for pixi

Cross-platform, multi-language package manager and workflow tool built on the foundation of the conda ecosystem.

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/pixi:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

The Chainguard Pixi Image is comparable to the Pixi Image from GHCR. However, the Chainguard image contains only the minimum set of tools and dependencies needed to function. This means it doesn't include things like a package manager.

Getting started

The quickest way of getting started with this image is by using docker:

docker run --rm -it cgr.dev/ORGANIZATION/pixi:latest

You can then run the pixi CLI via docker by running docker run:

docker run --rm -it cgr.dev/ORGANIZATION/pixi:latest pixi search numpy

Using channels: conda-forge

numpy-2.3.2-py314h488ef0c_2 (+ 15 builds)
-----------------------------------------

Name                numpy
Version             2.3.2
Build               py314h488ef0c_2
Size                7776504
License             BSD-3-Clause
Subdir              linux-aarch64
File Name           numpy-2.3.2-py314h488ef0c_2.conda
# ...

Example: HTTP server using external library

The following build demonstrates how a standard HTTP server could be implemented using Chainguard's Pixi development image.

First, create a project folder and change the working directory to that folder:

mkdir -p ~/pixi-http-server && cd $_

Next, write a file defining your HTTP server (main.py):

from flask import Flask

app = Flask(__name__)

@app.route("/")
def hello_world():
    return "<p>Hello, World!</p>"

Write a Dockerfile to define our image build:

FROM localhost:5005/pixi:latest-dev

WORKDIR /srv/http

COPY ./main.py /srv/http/main.py

RUN pixi init
RUN pixi add python flask

CMD [ ".pixi/envs/default/bin/flask", "--app", "main", "run", "--host", "0.0.0.0" ]

Build the image, tagging it pixi-http-server:

docker build -t "localhost/pixi-http-server:latest" .

Run the image exposing the port defined in the application code:

docker run -p 5000:5000 localhost/pixi-http-server:latest

You should see output similar to the following on the container logs:

 * Serving Flask app 'main'
 * Debug mode: off
 * Running on all addresses (0.0.0.0)
 * Running on http://127.0.0.1:5000
 * Running on http://172.17.0.3:5000
Press CTRL+C to quit

When fetching the contents of 127.0.0.1:8080 via a tool like curl, you will see the following:

curl 127.0.0.1:5000

<p>Hello, World!</p>

Documentation References

• Pixi Documentation
• Python documentation

What are Chainguard Containers?

Chainguard Containers are minimal container images that are secure by default.

In many cases, the Chainguard Containers tagged as :latest contain only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager. Chainguard Containers are built with Wolfi, our Linux undistro designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a -dev variant.

Although the -dev container image variants have similar security features as their more minimal versions, they feature additional software that is typically not necessary in production environments. We recommend using multi-stage builds to leverage the -dev variants, copying application artifacts into a final minimal container that offers a reduced attack surface that won’t allow package installations or logins.

Learn More

To better understand how to work with Chainguard Containers, please visit Chainguard Academy and Chainguard Courses.

In addition to Containers, Chainguard offers VMs and Libraries. Contact Chainguard to access additional products.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.