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

Build only option? #1451

Closed
ofir-petrushka opened this issue May 22, 2015 · 2 comments
Closed

Build only option? #1451

ofir-petrushka opened this issue May 22, 2015 · 2 comments

Comments

@ofir-petrushka
Copy link

We can either build or run the containers defined in docker-compose.
But can we have some images which are only for build since others relay on them but we don't want to actually run them?

Example:

Base container (docker hub)

  • language container
    • service container

So I want docker-compose build to build the "language container" to it will later be able to build the "service container" but I only want "service container" to run. I don't want docker-compose run to run "language container".

@ghost
Copy link

ghost commented May 24, 2015

The section in yml file does not refer to container (nor image) but service. So it makes no sence to have build-only services.
But compose can be more useful for development if I can point service to my image build system to provide image for it. Or if there was a way to include one to compose it self.

For now I recommend use image tag and build them by your self.

@dnephin
Copy link

dnephin commented May 24, 2015

There are a bunch of issues related to this (#942, #1284, etc). Going to close as a duplicate.

Also keep an eye on #1417 which should provide a better definition for what is "in scope" for compose.

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

2 participants