Pulp Container Plugin¶
You can use the
pulp_container plugin to extend Pulp so that you can host your own container registry and distribute containers in an on-prem environment.
You can synchronize from a range of Docker Registry HTTP API V2-compatible registries.
Depending on your needs, you can perform whole or partial syncs from these remote repositories, blend content from different sources, and distribute them throughout your organization using Pulp.
You can also build OCI-compatible images with Pulp Container and push them to a repository in Pulp so you can distribute private containers.
For information about why you might think about hosting your own container registry, see 5 reasons to host your container registry with Pulp. At the time of this article’s publication, there was no native way to perform import and exports to disconnected or air-gapped environments. This has since been introduced and is available.
If you’d like to watch a recent talk about Pulp Container and see it in action, check out Registry Native Delivery of Software Content.
If you are just getting started, we recommend getting to know the basic workflows.
Synchronize container image repositories hosted on Docker-hub, Google Container Registry, Quay.io, etc., in mirror or additive mode
Automatically Creates Versioned Repositories so every operation is a restorable snapshot
Download content on-demand when requested by clients to reduce disk space
Perform docker/podman pull from a container distribution served by Pulp
Perform docker/podman push to the Pulp Registry
Curate container images by filtering what is mirrored from an external repository
Curate container images by creating repository versions with a specific set of images
Build an OCI format image from a Containerfile and make it available from the Pulp Registry
Host content either locally or on S3
De-duplication of all saved content
Support disconnected and air-gapped environments with pulp import/export facility for synced container repositories
Some additional features are being supplied as a tech preview. There is a possibility that backwards incompatible changes will be introduced for these particular features. For a list of features currently being supplied as tech previews only, see the tech preview page.
How to use these docs¶
The documentation here should be considered the primary documentation for managing container related content. All relevent workflows are covered here, with references to some pulpcore supplemental docs. Users may also find pulpcore’s conceptual docs useful.
This documentation falls into two main categories: