-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multi-Stage builds on docker hub #1039
Comments
Thanks for the feedback. The Docker Hub and Docker Cloud automated build service will be adding support for multi-stage builds when this feature graduates to the stable channel (currently targeted for June as part of the 17.06 release). For more information on the Docker time-based release schedule, please see: https://docs.docker.com/engine/installation/#time-based-release-schedule |
Thank you for the prompt feedback! Feel free to close this issue unless you'd rather leave it open until that release. |
This reverts commit d2ccd7c.
@pkennedyr are we there there? |
I think not, my test app is still failing as of now: https://hub.docker.com/r/captncraig/multi-stage-test/builds/bu5tvny8jfhjzbsjg5rpw3s/ |
[UPDATE] Multi-stage builds are now available in Docker Cloud as part of the 5-30-2017 release: To take advantage of multi-stage builds (in Docker Cloud), select Edge (17.05.0-ce) as the Docker version of an automated repository.
We encourage you to try out Docker Cloud as this is where you will find support for this and many other autobuild features. |
@pkennedyr is the multi stage build still scheduled for docker hub for this june ? or has that been cancelled and only available in docker cloud ? |
Now, if dockerhub had multi-stage builds I could actually go ahead and use this in my images. docker/hub-feedback#1039
What's the conclusion - is Docker Hub getting multi-stage builds any time soon? |
[UPDATE to earlier post] Docker Hub will in fact support multi-stage builds when the automated build system is upgraded to 17.06.01 (target ETA July). We apologize for the confusion. |
I'm a bit confused...
So is Hub not going to go to 17.06 at any point? Or are you pulling the feature from CE / will it be flagged / etc.? |
@milsonian Apologies for the confusion, with availability of multi-stage builds in 17.06, this feature will also be available in Docker Hub when the corresponding upgrade to 17.06 occurs (ETA July). Note: Docker Cloud provides the ability to specify the Docker version (Stable or Edge) to use for an automated build, which enables access to the multi-stage build feature via the Edge channel today. |
That's great, thanks for the clarification @pkennedyr! |
@pkennedyr Any update on when in July we can expect this feature on the Hub? |
Current ETA: late July We are currently awaiting availability of 17.06.01 CE GA, which includes a bug fix for multi-stage builds. Once available, we will update the Automated Build system with this new version and multi-stage builds will be available in Docker Hub. |
FYI: https://blog.docker.com/2017/08/docker-enterprise-edition-17-06/ |
17.06.1-ce has dropped. Anxiously awaiting to see all my broken [multi-stage] builds start to run. |
@ph-One team is working on the upgrade for builders, please stay tuned. |
works on Docker Hub now for me. |
The Automated Build system has been updated with 17.06.01 CE, which enables multi-stage builds in Docker Hub. |
It worked - but now it's reverted to Docker EE 17.03.1? See https://hub.docker.com/r/gesellix/wait-for/builds/btfvjxwqgzrhdhxxz55ilj6/ for an example. |
Same problem here - https://hub.docker.com/r/krambox/node-web-app/builds/bcqh2dvtrvqlin3aub4wptt/ |
We have rollbacked the 17.06.1 release since some builds were failing due to the upgrade. |
thanks for the quick feedback @pchico83 |
17.06.1 is running in prod again |
@soulshake we just had a brief regression that caused some builders to run older versions of Docker. Your builds should all be running on |
Things works when I updated to version |
In trying to run multi-stage builds in a docker hub automated build:
Error parsing reference: "golang:1.7.3 as builder" is not a valid repository/tag: invalid reference format
It looks like docker hub is not using the version of docker that supports this yet. Is there a timeline for when support will be availible?
The text was updated successfully, but these errors were encountered: