Ability to deploy after a push to Docker Hub

[philp]

We've been trying out Shippable as the main component in a continuous delivery workflow, but have run into a little bit of an issue when it comes to deploying Docker images to AWS.

What we'd like to be able to do is this:

1. Commit code to Gt.
2. Have Shippable build and test the Docker container.
3. If successful, push the Docker container to Docker Hub, THEN:
4. Call eb deploy to trigger a deployment on AWS.

What we're trying to do is deploy the ready-built container from Docker Hub, so that our deployments can be tagged for easy rollbacks and other nice things. AWS allows us to use a Dockerrun.aws.json in place of a standard Dockerfile, in which we can define a specific container instance to pull from the Hub.

I can't see a way for us to easily do this with Shippable, because the after_success trigger happens BEFORE there is a push to Docker Hub — and that's the only place I can see to trigger the deployment.

Any thoughts?

[manishas]

@philp i believe you are correct... we deploy the container to AWS and we also push to DockerHub.

I'm following up to see if anyone has figured out a way to achieve your scenario...

[CADBOT]

@philp
Currently, you can't do this exact workflow, but we hope to have it available soon.

However, you can do something very close, if you're willing to circumvent docker hub. Both shippable and EB support docker build functionality. You can include a dockerfile in your repo, and both shippable and beanstalk can be configured to build you a new image on the fly. Specifically, shippable would build this image and use it to test your container, and after it passes it's test, would push your code to EB, where they would rebuild the image from the same docker file.

We recently released a blog about how to do this on our end: Docker build support

And here's EB's info on the topic EB dockerfile

[philp]

Thanks for getting back to me. And thanks for the references. The method you describe (doing a build from Dockerfile on EB) is the one we're currently using to work around this. But we'd love to be able to close the loop on our continuous delivery pipeline, so that the deployment uses the ready-built container form Docker Hub. There are all sorts of reasons for that, the main one being that we have better control over versioning and rollbacks, and just generally do things in a more consistent manne.

Would be great to know when you might be able to facilitate this kind of workflow. Would it be possible to have an after_push hook or something similar?

[CADBOT]

I see where you're coming from, and would love us to have support for this workflow myself!

I can't provide any promises as to the exact mechanism/implementation, but yes, something like that is what we have in mind.

As soon as a feature is available for this workflow, I'll be writing a blog for it at the shippable blog .

[chrisbrantley]

+1 for this. I'm trying to do the exact same thing and was surprised that it's not well supported on the CI tool landscape. Shippable gets us 99.9% there except we can't trigger the EB deployment AFTER a successful push to docker hub.

[melo]

BTW, since Amazon came up with ECS, EB got support for ECS and multi-container per instance deployments…

http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create_deploy_docker_ecs.html

[chrisbrantley]

I dont know how I missed that! Thank you!

On Saturday, March 28, 2015, Pedro Melo notifications@github.com wrote:

BTW, since Amazon came up with ECS, EB got support for ECS and
multi-container per instance deployments…

http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create_deploy_docker_ecs.html

—
Reply to this email directly or view it on GitHub
#1186 (comment).

Chris Brantley
Chief Technology Officer

Showroom Logic
13155 SW 134 ST Suite 107
Miami, Florida 33186
800.683.7940
chris@showroomlogic.com

[rvdwijngaard]

+1 for this from me too; I have configured aws ec2 container service (ecs) for one of our microservices; shippable with custom images is great and builds the new new docker images and pushes them to docker repository. The only thing which is left is to register a new task for my ecs cluster and update the service. This can be achieved with some scripting.

see https://blogs.aws.amazon.com/application-management/post/Tx32RHFZHXY6ME1/Set-up-a-build-pipeline-with-Jenkins-and-Amazon-ECS

an after_push event will makes this easy to achieve.

[cullophid]

+1

[mikehancock]

+1 for this, we use Digital Ocean, this feature would simplify our deployment pipeline

[manishas]

Closing as DUP of #824 where we're tracking all requests related to pushing to docker registries, tagging, etc.

This is near the top of our priority list now so expect an update soon!