Last updated
Was this helpful?
Last updated
Was this helpful?
The Default container registry is a flavor that comes built-in with ZenML and allows container registry URIs of any format.
You should use the Default container registry if you want to use a local container registry or when using a remote container registry that is not covered by other .
To specify a URI for a local container registry, use the following format:
To use the Default container registry, we need:
installed and running.
The registry URI. If you're using a local container registry, check out
the on the URI format.
We can then register the container registry and use it in our active stack:
This method uses the Docker client authentication available in the environment where the ZenML code is running. On your local machine, this is the quickest way to configure a Default Container Registry. You don't need to supply credentials explicitly when you register the Default Container Registry, as it leverages the local credentials and configuration that the Docker client stores on your local machine.
To log in to the container registry so Docker can pull and push images, you'll need to run the docker login command and supply your credentials, e.g.:
You may also need to set up required to log in to the container registry.
If you are using a private container registry, you will need to configure some form of authentication to login to the registry. If you're looking for a quick way to get started locally, you can use the Local Authentication method. However, the recommended way to authenticate to a remote private container registry is through .
If your target private container registry comes from a cloud provider like AWS, GCP or Azure, you should use the targeted at that cloud provider. For example, if you're using AWS, you should use the flavor. These cloud provider flavors also use specialized cloud provider Service Connectors to authenticate to the container registry.
Stacks using the Default Container Registry set up with local authentication are not portable across environments. To make ZenML pipelines fully portable, it is recommended to use to link your Default Container Registry to the remote private container registry.
To set up the Default Container Registry to authenticate to and access a private container registry, it is recommended to leverage the features provided by such as local login and reusing the same credentials across multiple stack components.
Linking the Default Container Registry to a Service Connector means that your local Docker client is no longer authenticated to access the remote registry. If you need to manually interact with the remote registry via the Docker CLI, you can use the to temporarily authenticate your local Docker client to the remote registry:
For more information and a full list of configurable attributes of the Default container registry, check out the .
Storing container images locally.
