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

Use output from other builds in target Dockerfile #21

Open
solsson opened this issue Feb 16, 2017 · 0 comments
Open

Use output from other builds in target Dockerfile #21

solsson opened this issue Feb 16, 2017 · 0 comments

Comments

@solsson
Copy link
Contributor

solsson commented Feb 16, 2017

This is a discussion on how build-contract relates to some core Docker design decisions.

Example: We have a FROM nginx build that needs to include a js file built with webpack, i.e. a quite lengthy Node.js/NPM execution. A typical build server like Jenkins would have Node.js installed locally and produce the js in a step prior to running docker build on the target image. A FROM node build could easily do the build, but we wouldn't get the file out of it, at least not at build time.

The target build could install the dependency + run the build + clean up, but that's quite messy and needs to make assumptions about the nginx image.

Relates to moby/moby#13026, where "Multi-stage building" looks like a similar concept.

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

No branches or pull requests

1 participant