flox-containers
Containerizing Flox environments with Docker/Podman. Use for creating container images, OCI exports, multi-stage builds, and deployment workflows.
Security Assessment
About flox-containers
The flox-containers skill provides a streamlined approach to containerizing Flox environments using Docker or Podman. It allows developers to package their entire Flox-managed development environment, including installed packages, environment variables, and hooks, into a portable container image. This eliminates the complexity of manually configuring environments across different systems and ensures consistency between development, testing, and production stages. By containerizing environments, teams can easily share setups, deploy applications reliably, and maintain reproducible workflows without worrying about host dependencies or configuration drift.
Key features of flox-containers include exporting Flox environments to files or directly into Docker/Podman runtimes, tagging container images, and supporting multi-stage builds for optimized container sizes. It provides options to containerize remote environments from FloxHub and supports piping container images directly into runtime tools. The skill also allows fine-grained configuration via a manifest, enabling users to specify commands to run, exposed ports, persistent volumes, working directories, user settings, labels, and stop signals. Containers automatically activate the Flox environment on startup, ensuring the runtime is immediately ready for interactive or non-interactive execution.
This skill is ideal for Python developers, DevOps engineers, and teams using Flox to manage their development environments. Use cases include deploying web applications, microservices, and data-processing pipelines consistently across local and cloud infrastructures. It is particularly beneficial for projects requiring reproducible environments, seamless integration with Docker/Podman workflows, and simplified collaboration between team members or across different machines.
FAQ
How do I export a Flox environment to a container file?
You can export your environment to a tar file using `flox containerize -f ./mycontainer.tar`. If no file is specified, it defaults to `{name}-container.tar`.
Can I use both Docker and Podman with flox-containers?
Yes, the skill supports both runtimes. You can specify the runtime using `--runtime docker` or `--runtime podman`, or let it auto-detect.
How do containers behave when I run them?
Containers automatically activate the Flox environment on startup. Interactive runs open a shell with the environment activated, while non-interactive runs execute commands with the environment applied.
Can I configure ports, volumes, and startup commands for my container?
Yes, you can configure these options in the `[containerize.config]` section of your manifest, including `exposed-ports`, `volumes`, `cmd`, `working-dir`, `user`, `labels`, and `stop-signal`.
Is it possible to containerize a remote Flox environment?
Yes, you can containerize a remote environment from FloxHub using the `-r <owner/env>` option.
Install flox-containers
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
flox/flox-agentic