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

multiple build targets #4544

Closed
xenoterracide opened this issue Feb 28, 2017 · 1 comment
Closed

multiple build targets #4544

xenoterracide opened this issue Feb 28, 2017 · 1 comment

Comments

@xenoterracide
Copy link

I've read #942 I don't see that that fixes this. In order to build our cluster currently we use the following "shell script"

docker build --pull -t dex/oracle-xe:latest etc/docker/oracle-xe/ &&
docker build -t dex/oracle-xe-with-sshd:latest etc/docker/oracle-xe-with-sshd/ &&


docker build --pull -t dex/tomcat:latest etc/docker/tomcat/ &&
docker build -t dex/dex:latest etc/docker/dex/

these prior images exists due to needing additional things (such ass sshd for legacy code) (or in tomcats case the fact that the default image is very insecure), so the images have been split so that the "base" image is more of a pure tomcat/oracle-xe. I would like to t be able to do this with compose. Maybe via

services:
    db:
        build:
           - ./oracle-xe
           - ./oracle-xe-with-sshd

or with nested (I think this is correct yaml)

services:
    db:
        build:
           - oracle-xe:
               context: ./oracle-xe
           - ./oracle-xe-with
@shin-
Copy link

shin- commented Feb 28, 2017

That's a bit outside of the scope of what Compose wants to do. I'd advise taking a look at dobi instead.

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

2 participants