Unable to recreate container with network type container:<name> that was on bridge network

[twigley]

Bug description

When recreating a container that was previously on the bridge with mapped ports and changing the network to container: the following error shows:

"conflicting options: port exposing and the container type network mode"

Expected behavior
The container to have been recreated sharing the network stack of the other container specified.

Steps to reproduce the issue:

Steps to reproduce the behavior:

1. Create 2 containers A and B on the bridge network with mapped ports
2. Recreate B while removing the exposed ports but setting the network to "container:A"
3. See error

Technical details:

• Portainer version: 1.19.2
• Docker version (managed by Portainer): 18.06.1-ce
• Platform (windows/linux): linux
• Command used to start Portainer (docker run -p 9000:9000 portainer/portainer):
  docker run --restart always -d -p 9000:9000 -v /mnt/path/portainer/:/data -v /var/run/docker.sock:/var/run/docker.sock --name portainer portainer/portainer:latest
• Browser:

Additional context
I've made sure in the UI at least that any mention of port exposing or port mapping is off.

[CatFoxVoyager]

Yeah, I have this issue too. Cannot set network to container. But if I do it in cli, it run perfectly

[agster27]

I have the exact same issue as well.

[immortalt]

I have the exact same issue as well.

[ellisonpatterson]

Same issue as well, how can you make this work since otherwise isn't the option useless?
Also an error occurs if you immediately switch the network back to host/bridge or whatever, and it complains that whatever was selected in the dropdown no longer exists, and you need to re-enter the container edit page to be able to deploy it again.

[CatFoxVoyager]

You need to use Docker command line to get this working unfortunately Le mar. 22 oct. 2019, à 12 h 38, Ellison Patterson <notifications@github.com> a écrit :

…

Same issue as well, how can you make this work since otherwise isn't the option useless? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#2316?email_source=notifications&email_token=AB5ATGMGSNV2LVXJ3ZM26LTQP4UBFA5CNFSM4FYES3N2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEB6MW6Q#issuecomment-545049466>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB5ATGLAQNLSBFWTEX3UG5TQP4UBFANCNFSM4FYES3NQ> .

-- [image: photo] *Jeremie Dufault* jedduff@gmail.com jeremiedufault.ca <http://facebook.com/jeremiedufault> <http://us.linkedin.com/in/jeremiedufault> <http://twitter.com/jedduff> <https://www.linkedin.com/in/jeremiedufault/>

[immortalt]

Finally I have to use the docker-compose to solve my problem.

[smcpeck]

@immortalt How did you do a container-mapped network with docker compose?

[C2BB]

Curious if there is an expected time frame for this fix?

[cyrus104]

This would be helpful, I am running several services on different ports but I want groups on the same IP. I have a macvlan setup and have setup a container with 1 ip and would like other containers to use the container options to use that same IP address with different ports.

[ghost]

Reproduced on 1.23.2

[viktorkho]

@immortalt Can you please tell us How did you do a container-mapped network with docker compose?

I have the same problem on clean compose.

BTW, seems this issue is not for Portainer itself, but for Docker/Compose stack.

[smcpeck]

@viktorkho
FWIW here, I've resorted to creating the needed container via the command line with the parameter:

--net=container:other_container

This creates the container as desired and then I can restart the container (if needed) in portainer. Still not ideal as I have to treat that container with care; I haven't attempted to recreate the container in portainer. But this approach has been getting me by from a functional POV here.

[ghost]

Reproduced on the development branch. Closing as this will be addressed via #3964 in v2.0

Note you now get the error: conflicting options: dns and the container type network mode as we now allow setting dns

[duhruh]

@itsconquest is this fixed on a branch or something, still am getting the error and I would really like to not have to deploy the container via the command line as suggested above 😢

[ghost]

@duhruh a fix is currently merged in the develop branch pending release in v2.0 of Portainer