Support Docker versions newer than v1.9.1

bump. We’d really like to have this too.


Would love to get some status here.

Can we have a timeline?

… update … where is the docker update…

1 Like

This is not an ETA like I know many of you want, but to answer the question of, “What is CircleCI doing about supporting Docker v1.10+”, we now have an announcement for things to come:


It’s almost 2017 now, any update on a newer version of docker? or a workable fix for docker exec.


Same here, wonder how to at least get 1.12 running in CircleCI? Manual upgrade inside the circle.yml?

Edit: Seems you can at least go from 1.9 to 1.10 with the following configuration:

    - curl -sSL | bash -s -- 1.10.0
1 Like

Another shameless +1. We applied for the circle ci 2.0 beta and I hope we get it.

Thanks for your patience with this everyone.

The private beta of CircleCI 2.0 is being rapidly rolled out to people who apply here:

This will allow you to specify the Docker version you want.

Open beta will follow as soon as we’re ready. Please subscribe to our Announcements to be notified when it’s available.

You can side load docker by adding the follwoing. Remember to remove docker from services list if you have it.

    - curl -fsSLO && sudo tar --strip-components=1 -xvzf docker-1.13.1.tgz -C /usr/local/bin
    - sudo container=yes docker daemon: { background: true }

+1 to this thread and also want to request for native image caching rather than having to save images as tars like current documentation states.

CircleCI 2.0 is now in Beta and you can start building on our latest platform by signing up at

2.0 provides native docker support, faster build performance and greater environment control.

This will be how we’re going to support newer Docker versions going forward.

Docker builds have major performance issues with CircleCI 2.0 (basically caching doesn’t work reliably), so how can this be the suggested solution?

A post was split to a new topic: Supporting Docker builds is one hack over the other with 2.0