Skip to content

Container Registry FAQ

View as Markdown

Which regions is Container Registry available in?

Section titled “Which regions is Container Registry available in?”

Delhi. See Create a registry project.

No. Every registry project is private, and Docker pulls from it after logging in with an access token. See Create an access token.

Up to 20 in each MyAccount project. Only projects that have finished creating count toward the 20. See Create a registry project.

No. A project’s name is fixed when you create it, and it is part of every image path. See Create a registry project.

Can two accounts use the same project name?

Section titled “Can two accounts use the same project name?”

No. Registry project names are unique across the whole registry. Choose a name that no registry project uses yet, in your account or in any other. See Create a registry project.

An access token: its Token Name, such as e2ecr-12345+laptop, is the username, and its Token Value is the password. See Create an access token.

How many access tokens can a registry project have?

Section titled “How many access tokens can a registry project have?”

Five. To make room for a new one, delete a token you no longer use. See Manage an access token.

Yes. Pull is always checked, and Push is optional, so leave Push clear. You can add or remove Push later with Edit. See Create an access token.

No. The value is shown once, when you create or reset the token, because E2E does not keep it. Reset the token to get a new value. See Manage an access token.

Can I delete images from a script or CI job?

Section titled “Can I delete images from a script or CI job?”

No. An access token can pull and push only, so a delete made with a token is refused. Delete repositories and artifacts in MyAccount, or schedule Image Cleanup to remove untagged images for you. See Delete a project, repository, or artifact.

Yes, once you choose a schedule. Auto-Cleanup Schedule starts at Off; choose Daily to run at 00:00 UTC every day, or Weekly to run at 00:00 UTC every Sunday, and click Save Schedule. See Clean up unused images.

No. Cleanup always keeps every tagged image and removes every untagged image, with no age or count to set. To keep an image, keep a tag on it. See Clean up unused images.

Are images scanned for vulnerabilities automatically?

Section titled “Are images scanned for vulnerabilities automatically?”

Yes. Every image is scanned when you push it, and you can scan a project, a repository, or an artifact again. See Scan a project, repository, or artifact.

Can I stop vulnerable images from being pulled?

Section titled “Can I stop vulnerable images from being pulled?”

Yes. Check Prevent vulnerable images from running. and choose a Severity Level; images with vulnerabilities at that level and above cannot be pulled. Set it when you create the project, or later on its Configuration tab. See Scan a project, repository, or artifact.

Can I copy images from Docker Hub or another registry into my project?

Section titled “Can I copy images from Docker Hub or another registry into my project?”

Yes. Add the other registry as a source registry, then create a replication rule that copies images from it into your project. See Add a source registry.

Can a replication rule copy images into a different project?

Section titled “Can a replication rule copy images into a different project?”

No. A rule always copies into the project that holds it. To fill another project, create the rule in that project. See Create a replication rule.

Yes, for a project whose peak stays at 1 GB or less. A registry project is billed on its peak storage in the calendar month. A project whose peak stays at 1 GB or less is free; once the peak passes 1 GB, the whole peak is billed, rounded up to whole GB. For example, a 1.2 GB peak is billed as 2 GB. A project has no storage cap. For current prices, see E2E’s pricing page.

Am I billed for the whole month if my project exists for only part of it?

Section titled “Am I billed for the whole month if my project exists for only part of it?”

No. A project that exists for only part of a month is charged its peak storage for the hours it existed that month.

Yes, from the next month. Each month is billed on its peak storage, so the current month keeps its peak. When you delete an image or a repository, Storage Used goes down right away, and the next month’s bill starts from the smaller size. See Clean up unused images.

Am I billed for a project that failed to create?

Section titled “Am I billed for a project that failed to create?”

No. A project that reads Creating or Failed is not billed. See Troubleshooting Container Registry.

What should I do if the registry returns 500 or 502?

Section titled “What should I do if the registry returns 500 or 502?”

A 500, a 502, or an unknown error is a problem on the registry’s side; your machine and token need no change. Run the command again after a few minutes, and contact support if it keeps failing. See Troubleshooting Container Registry.

No. Deleting a project deletes its replication rules, source registries, repositories, and artifacts, and none of it can be recovered. See Delete a project, repository, or artifact.