Skip to main content
With a Minimus account, you can get more out of Minimus:
  1. Create private images with a custom list of packages, certificates, env vars, and more.
  2. Adapt private images to your CI/CD pipelines using minicli
  3. Set up actions
  4. Sync Minimus images to your private registry
  5. Set up user management and SSO for the team

​
1. Create your first private image

If you would like to customize a Minimus image by adding packages, configuration files, certificates, or environment variables, you can use Minimus Creator to build your own private image. Minimus will maintain, update, and scan your private images just as if they were public images. If you are migrating from Alpine, Debian, or other distro-based images, you can learn more about how to build a custom image off Static with only the packages of your choice. You can also see our recommendations for adjusting Dockerfiles in more complex scenarios by temporarily escalating privileges, using Python virtual environments (venv), etc. See Going Distroless

​
2. Connect your registry and pipelines

You’ll want to check that you meet the networking requirements. If you prefer to pull Minimus images through a third-party registry, you can set up syncing with Google Artifact Registry or JFrog Artifactory. With a Minimus image subscription, you will also be able to sync images to a self-hosted private registry, even if it is air-gapped.

​
3. Enable supply chain protection

Minimus supply chain protection guards against malicious packages and tampered dependencies in your private images. Once enabled, every package included in a private image is verified against the Minimus supply chain policy before the image is built.
Last modified on June 24, 2026