Container Registry

Container Registry is a private registry for your Docker container images. You create a registry project, create an access token for it, and log in with Docker to push and pull your images. Your images live at registry.e2enetworks.net/<project-name>/<repository>, where <project-name> is your registry project’s name and <repository> is the name you push an image under. Each image you push is an artifact in its repository: one exact image, named by its digest, with any tags you gave it. Every registry project is private: Docker pulls from it after logging in with one of the project’s access tokens.

What you can do

• Create a registry project to hold your images.
• Create an access token that Docker logs in with, to pull images or to pull and push them.
• Push and pull images with Docker, using the commands the portal gives you.
• Pull images from a Kubernetes pod with a secret that holds an access token.
• Manage an access token: change its expiry or permissions, reset its value, turn it off, or delete it.
• Scan a project, repository, or artifact for known vulnerabilities, and keep vulnerable images from being pulled.
• Add a source registry, such as Docker Hub or AWS ECR, to copy images from.
• Create a replication rule that copies images from a source registry into your project, when you run it or on a schedule.
• Clean up unused images to remove untagged images, on a schedule or when you choose.
• Delete a project, repository, or artifact when you have finished with it.

Where to start

Start with Get started with Container Registry. If something goes wrong, Troubleshooting Container Registry has the fixes, and the Container Registry FAQ has short answers.