Docker Compose Version change and setting Network during Build process about isle HOT 3 CLOSED

+1

Questions:

• Why isn't docker-compose respecting the build context's network setting?
• Is trying with just docker build a step in figuring this out, as it says you can pass the --net= arg on the CLI?
• How can we bring up a container during the build on a specific docker network so that stack components dependent can communicate?

Link provided by @g7morris is important first steps to try and figure this one out; assuming it is even possible without getting outside the box (e.g. proxying or routing) and so far out of scope it's not worth effort during Alpha stages)

tl;dr: Docker: respect build network specified when you're building a services stack. Especially if they're clearly depends_on: and therefore required during build? right.

from isle.

I think this ticket may be closed as it is superseded by a number of tickets which expand on this issue more in depth and (some) are solved as we're going. I'm not sure if this ticket needs to sit queued.

@g7morris thoughts? if you concur would you do the honor?

from isle.

The need for this has been deprecated by the new image structure.
Run issues do not exist for end-users.

from isle.