Skip to content
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

Add multi stage build best practices #5481

Merged
merged 1 commit into from
Dec 20, 2017
Merged

Add multi stage build best practices #5481

merged 1 commit into from
Dec 20, 2017

Conversation

tjamet
Copy link
Contributor

@tjamet tjamet commented Dec 11, 2017

Hi,

May I propose to add a best practice section regarding multi stage builds. Suggesting users best practices to benefit build cache, not rebuilding unnecessary things, for building applications while keeping very small final images.

@joaofnfernandes
Copy link
Contributor

It seems that we already have some information about multi-stage builds in this article on line 64. Do you care to move your changes closer to that, instead of putting them in the section The Dockerfile instructions?

@@ -167,6 +167,53 @@ the command string itself will be used to find a match.
Once the cache is invalidated, all subsequent `Dockerfile` commands will
generate new images and the cache will not be used.

### Optimizing [multi-stage builds](multistage-build.md)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No links or Markdown in titles

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

@mdlinville mdlinville merged commit 3c44bc7 into docker:master Dec 20, 2017
@tjamet tjamet deleted the multistage branch December 20, 2017 23:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants