docker-pixi-project-offline

Build and verify Pixi projects in Docker for air-gapped environments.

7|1|Updated Jul 10, 2025
One-click install
npx skills add https://github.com/igamenovoer/magic-context --skill docker-pixi-project-offline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docker-pixi-project-offline
Source: https://github.com/igamenovoer/magic-context/tree/main/skills/air-gapped/docker/docker-pixi-project-offline
Command: npx skills add https://github.com/igamenovoer/magic-context --skill docker-pixi-project-offline

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires docker, pixi, rsync, and includes scripts (resource) components.

What problem does it solve?

This Skill solves the challenge of preparing Pixi-managed projects for air-gapped environments by building and validating them inside Docker and producing a portable WORKDIR/product directory for offline delivery.

Core Features & Use Cases

  • Docker-based build: Build and verify a Pixi project inside a container to ensure reproducibility.
  • Offline packaging: Produce a standalone WORKDIR/product directory that can be shipped to air-gapped environments.
  • Single-source tooling: Includes a set of scripts under scripts/ to automate host/container workdir creation, packaging, and final verification, reducing manual steps.

Quick Start

Run the provided scripts to stage a project into a WORKDIR, build with Docker, verify, and generate a portable product in WORKDIR/product. Then use the make-archive-ready-product.sh to create the deliverable.

Frequently Asked Questions about docker-pixi-project-offline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a Pixi project for deployment in an air-gapped environment?

To build a Pixi project for an air-gapped environment, you stage the project into a workdir, run pixi install inside Docker, verify it, and generate a self-contained product directory with envs.sh and bootstrap-project.sh scripts.

What is the best way to package Pixi caches and resources for offline delivery?

Packaging Pixi caches for offline delivery involves using Docker to build and validate the project, then producing a portable workdir product directory that bundles all resources and caches for transfer to disconnected systems.

Do I need Docker and rsync to prepare a Pixi project for offline builds?

Yes, Docker, Pixi, and rsync are required dependencies. Docker builds and verifies the project reproducibly, while rsync stages the host and container workdirs before generating the final offline product.

Can I verify a Pixi project inside a container before shipping it to an air-gapped system?

Yes, the Skill performs optional verification inside Docker after running pixi install. This ensures the staged workdir and Pixi caches are fully validated before generating the portable product directory.

What scripts are included for automating offline Pixi builds and packaging?

The Skill includes scripts under the scripts/ directory to automate host and container workdir creation, build verification, packaging, and final archive generation via make-archive-ready-product.sh for air-gapped delivery.

When should I use Docker-based offline builds instead of standard Pixi installs?

Use Docker-based offline builds when you need to deploy Pixi-managed projects to air-gapped systems. It ensures reproducibility by validating dependencies inside a container before creating a standalone portable product directory.