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 Apr 29, 2024. It is now read-only.
when using the new 2.0 file format compose creates a new docker network every time, so if you do docker inspect on any of the containers you get something like this:
Thanks for the detailed write-up! Docker-Compose 2.0 came out after this plugin was released but we fully intend to support it. I published a new SNAPSHOT release that contains a fix to read the new 2.0 network information if it exists:
Hi,
when using the new 2.0 file format compose creates a new docker network every time, so if you do
docker inspect
on any of the containers you get something like this:Note that
Gateway
is empty, so the current approach to determine the host gives an empty string.Everything works as expected with 1.0 compose format.
Not sure what are your plans regarding 2.0, but I suppose a warning in the docs would be nice at the very least :)
The text was updated successfully, but these errors were encountered: