Self-hosting an atproto container registry

This is a part of a series of blog posts on self-hosting atproto components. The previous ones are [Self-hosting your PDS] and Self-hosting and Tangled. atcr.io is a container registry on atproto, it’s a place where you can push your Docker and other container images to, and then fetch them and run them in just about any place, from a local Docker Compose, to hosted services like Railway, or self-hosted PaaSs like Dokploy. While atcr.io offers a free managed registry server, you can also run your own, called the hold. So we will! The guide As usual, you need to have a domain or subdomain ready to point at your hold. You’ll also need one for your self-hosted object storage, if you’re not using an existing one. Let’s assume you have s3.example.com and hold.example.com. Okay, if you’ve read the previous parts you know we start with the Caddy file. You’ll also need a .env file, we’ll get some of the values for it later. hold.example.com { reverse_proxy hold:8080 } s3.example.com {…