3 ms·
Yup, pretty much. We actually were using Docker Hub but they went down a few times so we are going to try setting up a private registry. We also tried Docker H
by alvinchow86 12y ago
Yup, pretty much.
We actually were using Docker Hub but they went down a few times so we are going to try setting up a private registry. We also tried Docker Hub's "Automated Build" service but it doesn't do any layer caching between builds so we found it way too slow.
One thing I'd recommend is at least installing the Docker service itself on the AMI (spinning up EC2 instances, especially on Opsworks, is slow enough as is)
- Gigablah 12y agoI actually trust Docker Hub more compared to a private registry setup... had so many hard to debug EOF errors, registry container crashes, etc. But the Docker Hub is also a single point of failure, so now I'm considering just having our CI service dump (docker save) the container build to a tarfile and send it to S3, then having the destination host download it and run docker load. Docker's handling of layers is excruciatingly slow, anyway.
- toomuchtodo 12y agoWe use private registry instances behind an ELB, with the containers stored in S3. When production counts on the registry being available, you've got to ensure reliability of the service and durability of the underlying container data.