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

Support build containers #1257

Closed
fabiokung opened this issue Apr 6, 2015 · 2 comments
Closed

Support build containers #1257

fabiokung opened this issue Apr 6, 2015 · 2 comments

Comments

@fabiokung
Copy link

As specified here: jamiemccrindle/dockerception.

Currently build in a docker-compose.yml file does not allow custom build pipelines (other than docker build -t <tag> <path>) to be specified. Either extend what can be done with the build property, or introduce something else to make it possible to build runtime containers using an intermediate build container that outputs the build context as a tar stream.

@dnephin
Copy link

dnephin commented Apr 6, 2015

I've used shipwright myself as an alternative to docker-compose build, but this feels (to me at least) like something that should remain external to compose itself. There is the potential to add a lot of complexity to compose, when it's not really necessary. It's just as easy to do:

run-my-fancy-build-tool
docker-compose up -d --no-build

And have all the services in the docker-compose.yml just use image:.

Related #693

@fabiokung
Copy link
Author

I'd be OK with that too, but it seems like on those cases when compose is useful (multiple containers being run) there will be multiple containers to be built. It's OK to leave it outside compose completely, but soon we may end up with another build-compose tool.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants