Container Registry FAQs

What is the IONOS Container Registry?

IONOS Cloud Container Registry is a managed service that provides users with a dedicated Docker registry or multiple registries as part of their contract. This enables them to host their own Docker images without the need for an external provider (such as Docker Hub).

How to create a Container Registry?

Refer to the create container registry workflow.

What are the main benefits of the IONOS Container Registry?

IONOS Container Registry is totally private and requires authentication to access it. It resides in the same infrastructure as your other **IONOS Cloud infrastructure**. Any unauthenticated user will not be able to access the registry contents. IONOS Container Registry software ensures that everything software being used is up to date and resilient. You don't need to use mK8s capacity to run (and then manage) your own Container Registry.

Can I get admin credentials for the container registry?

Refer to the create registry token workflow.

How can I access the Docker Registry HTTP API V2?

Refer to the Docker Documentation and go to the Docker Registry HTTP API V2 documentation.

What are the limits for the IONOS Container Registry?

Following are a few limitations for the IONOS Container Registry:
  • You cannot choose your encryption keys (Trust-No-One) when encrypting data at rest; the Container Registry platform manages the keys.
  • There is no way to grant repository access permissions to push, pull and/or delete from a specific repository.
  • There is no security scanning service so that you can receive feedback when the artifacts are exposed to a security risk.
  • An unauthenticated user will not be able to access the registry contents.
  • To have a registry, you need authentication and authorization, and the registry's contents must not be accessible to unauthenticated users.

Can repositories be public?

All container registries are available on the public internet but cannot be accessed without a token with the correct rights.