4 min read
|
Saved February 14, 2026
|
Copied!
Do you care about this?
DigitalOcean now allows Professional Plan users to create and manage up to 10 container registries under a single team. This update improves organization for different environments and enhances compliance with data residency requirements. Users can manage these registries through a new API and command-line tool.
If you do, here's more
DigitalOcean has launched a significant update to its container registry service, allowing users on the Professional Plan to create and manage multiple registries under a single team. Each team can now have up to 10 registries, which enables better organization for various deployment environments such as development, staging, and production. This change addresses the previous limitation where each team could only maintain one registry, providing more flexibility in managing container images.
The update includes enhanced capabilities for regional performance, allowing users to provision registries in specific locations to reduce latency and costs associated with data transfers. It also supports compliance with regulations like GDPR by enabling users to store container artifacts within specific geographical boundaries. The new multi-registry feature lays the groundwork for future enhancements, including registry mirroring and geo-replication.
Managing these registries is streamlined through an updated API, which requires users to utilize the new endpoint, v2/registries, for all operations. The legacy endpoint remains for backward compatibility but wonβt support multi-registry tasks. Users can perform various actions via API calls, such as creating, listing, and deleting registries, as well as managing garbage collection for untagged manifests. In parallel, the command-line tool, doctl, has also been updated to include support for managing multiple registries, with distinct commands aligned to the new API structure.
Users need to keep in mind that while they can create multiple registries, thereβs a limit of 10 per team on the Professional Plan. If a user wants to downgrade to a lower plan, they must first delete any additional registries until only one remains.
Questions about this article
No questions yet.