Report this

What is the reason for this report?

DigitalOcean Container Registry - Spaces Region

Posted on April 29, 2020
  • I have set up a DigitalOcean Container Registry which is backed by Spaces.
  • I host my applications primarily out of NYC regions
  • The Container Registry created its storage space in AMS3 not NYC3.

The problem:

  • This would mean added latency when pushing and pulling images from NYC.
  • There would also be transfer costs pulling the images from AMS3 to NYC regions.

Questions:

  • Is this a shortcoming of Early Release status, not being able to pick a region?
  • There is no region option in the API either.
  • It would also seem if region was selectable it would have to be part of the container registry URL such as nyc3.registry.digitalocean.com.

I posed this to DO support in a ticket, but I don’t think it reached the right team, because they haven’t added Containers as an option in their support drop down options, and they reply was ultimately that person didn’t know. They said they’d try and find out, but it’s been a while, so I wondered if anybody else had the same concern or more knowledge about where it’s going.

Thanks, Scott



This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Heya,

Just came across this answer and decided to write some general guidelines for anyone who comes across this in the future despite the old question.

As of this moment, users don’t have the ability to set a particular region during the early release phase.

As you’ve stated, this option of choosing your desired region isn’t available in the API yet. But, rest assured that our development team is constantly working on feedback and we’re expecting improvements in future releases.

I’m sorry to hear about any inconvenience that this issue might have caused you. Your concern might have not reached the appropriate team for which I apologize.

We would certainly want to ensure that your concerns are addressed and will do our best to expedite any pending inquiries.

For any future updates on this feature, please refer to the DigitalOcean Docs.

Hope this clarifies your concerns.

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.