{"componentChunkName":"component---src-templates-blog-post-js","path":"/blog/docker-registry-becomes-unavailable-and-returns-503","result":{"data":{"allGhostPost":{"edges":[{"node":{"title":"Docker Registry Becomes Unavailable and Returns \"503 Service Unavailable\" on All Requests With The S3 Storage Driver","html":"<p>I just ran into this issue myself so I hope this helps others. I set up a new Docker Registry following <a href=\"https://docs.docker.com/registry/deploying/\">the documentation</a> and configured the S3 storage driver to use DigitalOcean Spaces.</p>\n<p><strong>I created a new Space to host the registry's data.</strong></p>\n<p>That was the issue. Docker Registry (now called Distribution?) didn't like the fact that the Space (or S3 bucket) was empty. Per <a href=\"https://github.com/docker/distribution/issues/2292#issuecomment-378521123\">this suggestion on the related GitHub issue</a>, I uploaded a random file to my Space. That took care of the issue.</p>\n<p>For the record, here's the config I'm using:</p>\n<pre><code>storage:\n  s3:\n    region: us-east-1\n    regionendpoint: https://ams3.digitaloceanspaces.com\n    bucket: SPACE NAME HERE\n    encrypt: false\n    secure: true\n    v4auth: true\n    chunksize: 5242880\n    rootdirectory: /\n</code></pre>\n<p>with the Spaces API tokens passed through these two env vars:</p>\n<pre><code>REGISTRY_STORAGE_S3_ACCESSKEY=\nREGISTRY_STORAGE_S3_SECRETKEY=\n</code></pre>\n<blockquote>\n<p><a href=\"https://kmln.sr/70nk4RY\">Config source</a>—thanks ASB! 😄<br>\nI had to remove the <code>keyid: mykeyid</code> line for it to work.</p>\n</blockquote>\n","published_at":"2018-08-17T00:07:34.000+03:00","slug":"docker-registry-becomes-unavailable-and-returns-503","tags":[],"plaintext":"I just ran into this issue myself so I hope this helps others. I set up a new\nDocker Registry following the documentation\n[https://docs.docker.com/registry/deploying/]  and configured the S3 storage\ndriver to use DigitalOcean Spaces.\n\nI created a new Space to host the registry's data.\n\nThat was the issue. Docker Registry (now called Distribution?) didn't like the\nfact that the Space (or S3 bucket) was empty. Per this suggestion on the\nrelated\nGitHub issue, I uploaded a random file to my Space. That took care of the issue.\n\nFor the record, here's the config I'm using:\n\nstorage:\n  s3:\n    region: us-east-1\n    regionendpoint: https://ams3.digitaloceanspaces.com\n    bucket: SPACE NAME HERE\n    encrypt: false\n    secure: true\n    v4auth: true\n    chunksize: 5242880\n    rootdirectory: /\n\n\nwith the Spaces API tokens passed through these two env vars:\n\nREGISTRY_STORAGE_S3_ACCESSKEY=\nREGISTRY_STORAGE_S3_SECRETKEY=\n\n\nConfig source [https://kmln.sr/70nk4RY]—thanks ASB! 😄\nI had to remove the keyid: mykeyid  line for it to work.","meta_description":null}}]}},"pageContext":{"slug":"docker-registry-becomes-unavailable-and-returns-503","prev":"transparent-vue-wrapper-components","next":"dropin-chatops-turning-existing-workflows-and-scripts-into-slack-commands"}},"staticQueryHashes":["3649515864"]}