Container network name not cleared after switching to bridge network in dropdown

[ghost]

Bug description
After selecting a container network, switching to bridge does not remove the container name from the network name.

Expected behavior
Switching back to a bridge network should clear the container name from the network name.

Portainer Logs
NA

Steps to reproduce the issue:

1. Go to Container create view
2. Select a container network from the dropdown
3. Select a container
4. Switch back to bridge network
5. Click deploy
6. See error
   

Technical details:

• Portainer version: 1.23.0
• Docker version (managed by Portainer): 19.03.05
• Platform (windows/linux): Linux (Ubuntu 18.04)
• Command used to start Portainer (docker run -p 9000:9000 portainer/portainer): docker run
• Browser: FireFox

Additional context
Behaviour present in 1.21.0 aswell, so does not appear to be a bug as a result of #2657

[ghost]

Reproduced on 1.23.2

[jamescarppe]

We have been unable to replicate this in newer versions of Portainer so we're closing this issue.

[ghost]

Ahh there was a missing step required to reproduce this, you have to also select a container after selecting the container network time. I have just reproduced this now on the latest version of portainer, and have updated the description as this is still a bug

[github-actions]

This issue has been marked as stale as it has not had recent activity, it will be closed if no further activity occurs in the next 7 days. If you believe that it has been incorrectly labelled as stale, leave a comment and the label will be removed.

[github-actions]

Since no further activity has appeared on this issue it will be closed. If you believe that it has been incorrectly closed, leave a comment mentioning portainer/support and one of our staff will then review the issue. Note - If it is an old bug report, make sure that it is reproduceable in the latest version of Portainer as it may have already been fixed.

[gausie]

Could this please be reopened?

[procheeseburger]

its odd that things just get closed because no one has responded.. this is still an issue Aug 2022

[jamescarppe]

It looks like when @itsconquest reopened this he missed readding the necessary labels to prevent it from being stalebotted again. I'll fix this up and reexamine the bug to see where it's at.

[jamescarppe]

I have been able to replicate the behavior on the latest version now, and will be following up with the engineering team as to a fix.