Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot save mutiple hosts file entries under advanced network setup #1855

Closed
ghost opened this issue May 2, 2018 · 7 comments
Closed

Cannot save mutiple hosts file entries under advanced network setup #1855

ghost opened this issue May 2, 2018 · 7 comments

Comments

@ghost
Copy link

ghost commented May 2, 2018

Bug description

The UI allows me to add multiple host file entries under the advanced network setup but when I save and provision the container is only saves and applies the first host file entry and all other entries are lost.

Expected behavior

The ability to define multiple host file entries and for them to be saved to the running docker container and then displayed in the UI.

Steps to reproduce the issue:

Steps to reproduce the behavior:

  1. Go to advanced network settings for an existing or new docker container
  2. Add multiple host file entries
  3. Deploy the container
  4. Go in and edit the container
  5. Only the first host file entered is displayed

Technical details:

  • Portainer version: 1.16.5
  • Docker version (managed by Portainer): 18.03.1-ce
  • Platform (windows/linux): Linux
  • Command used to start Portainer (docker run -p 9000:9000 portainer/portainer): docker run -d -p 9000:9000 -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer
  • Browser: Chrome
@deviantony
Copy link
Member

Hey @ollieatseats

I'm not able to reproduce this issue, see the screenshots below:

portainer

portainer1

Could you share the exact informations you're using?

@ghost
Copy link
Author

ghost commented May 3, 2018

I started a new container hello-world:linux and added the following two records

config.management.local:10.22.8.9
client.management.local:10.22.8.9

When the container started it only persisted the first record so I went in and added the second record again and it still did not persist it.

I am running the docker host on a fully patched Ubuntu 16.04 Azure VM (DSv2) with 18.03.1-ce installed. If you cant recreate it, its probably just my environment, it just seems strange,

@deviantony
Copy link
Member

I went in and added the second record again and it still did not persist it.

What do you mean by that? Did you alter the container manually?

@ghost
Copy link
Author

ghost commented May 3, 2018

I added the second host name via the UI again and redeployed the container and it still not add the second value.

@deviantony
Copy link
Member

@ollieatseats via the container creation of container edition ?

@ghost
Copy link
Author

ghost commented May 3, 2018

When I create the container I add the following host entries:

before

Once the container is created I then go in to edit the host entries to redeploy the container:

after

@deviantony
Copy link
Member

Ah, so this is related to container-edition ! I'll investigate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant