Re:Migrating from Heroku to AWS using Docker
by alvinchow86 on Saturday April 04, 2015 @01:50AM
(#9320056)
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)
Re:Migrating from Heroku to AWS using Docker
by Gigablah on Saturday April 04, 2015 @05:26AM
(#9320438)
I 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.
Re:Migrating from Heroku to AWS using Docker
by toomuchtodo on Saturday April 04, 2015 @01:45PM
(#9321528)
We 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.
Re:Migrating from Heroku to AWS using Docker
by andrewstellar on Saturday April 04, 2015 @12:03AM
(#9319854)
Great, thank you!
Use Jenkins (or preferred build system) to fetch the Dockerfile, your app, build the Docker container, and then docker push to your own private docker registry.
Bake your AMIs with your Docker image (tags are your friend). You don't want to have to scale and find out you're having problems fetching Docker images from your private registry. You'll still be using config management for the underlying Docker host.
Hope this helps!