You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 16, 2021. It is now read-only.
I'm trying to use a compose manifest where an external default network is being defined. However, it seems like the configuration isn't being honored.
To illustrate my problem, I put together an example repo (note the extra branch I have created for this purpose). The external network is defined here. Starting that compose file with docker-compose like
docker-compose -f simple.yml up
and inspecting the curl (client) container, I see the network being in use:
I'm trying to use a compose manifest where an external default network is being defined. However, it seems like the configuration isn't being honored.
To illustrate my problem, I put together an example repo (note the extra branch I have created for this purpose). The external network is defined here. Starting that compose file with docker-compose like
and inspecting the curl (client) container, I see the network being in use:
Doing the same via libcompose through my example application started with
go run main.go -f simple.yml
, the default compose network is referenced:I have also tried to tweak some settings during project creation, but to no avail.
Happy to provide more details if needed.
Thanks :)
/cc @vdemeester
The text was updated successfully, but these errors were encountered: