Skip to content
This repository has been archived by the owner on Dec 11, 2020. It is now read-only.

Container network fixes #104

Merged
merged 13 commits into from
Oct 25, 2018
Merged

Container network fixes #104

merged 13 commits into from
Oct 25, 2018

Conversation

@mavogel mavogel added this to the v1.1.0 milestone Oct 19, 2018
@mavogel mavogel self-assigned this Oct 19, 2018
@ghost ghost added the size/XS label Oct 19, 2018
@ghost ghost added size/L and removed size/XS labels Oct 19, 2018
@mkeeler
Copy link
Member

mkeeler commented Oct 22, 2018

This seems to break passing a network name in the "network_mode" configuration for a container. I like this change but it definitely should be considered a breaking change.

@mavogel
Copy link
Contributor Author

mavogel commented Oct 23, 2018

@mkeeler this is coming from e07e383 which is already merged into the master. I guess network_mode was never intended to pass a network name. I wonder why it worked in the past. But you're right it's a breaking change

Update:

I guess network_mode was never intended to pass a network name

I was wrong ;) According to https://docs.docker.com/engine/api/v1.37/#operation/ContainerCreate

Network mode to use for this container. Supported standard values are: bridge, host, none, and container:<name|id>. Any other value is taken as a custom network's name to which this container should connect to

So I'll fix this breaking change before releasing in #107. Thx for pointing out!

@mavogel mavogel merged commit 2360eb0 into master Oct 25, 2018
@mavogel mavogel deleted the fix-container-networks branch October 25, 2018 05:22
@mavogel mavogel mentioned this pull request Nov 6, 2018
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants