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

Auto suggest for images on multinode swarm suggests the same image multiple times #3422

Closed
ghost opened this issue Dec 3, 2019 · 2 comments · Fixed by #3425
Closed

Auto suggest for images on multinode swarm suggests the same image multiple times #3422

ghost opened this issue Dec 3, 2019 · 2 comments · Fixed by #3425
Assignees
Labels
Milestone

Comments

@ghost
Copy link

ghost commented Dec 3, 2019

Bug description
Auto suggest for images on multinode swarm suggests the same image multiple times

Expected behavior
Auto suggest should only suggest an image once, even if the same image is present on different nodes

Steps to reproduce the issue:

  1. Pull same image on multiple nodes
  2. Get multiple auto suggestions

Technical details:

  • Portainer version: develop
  • Docker version (managed by Portainer): 19.03
  • Platform (windows/linux): linux
  • Command used to start Portainer (docker run -p 9000:9000 portainer/portainer): portainer agent stack
  • Browser: firefox
@ghost ghost added this to Need triage in Bug triage via automation Dec 3, 2019
@deviantony deviantony removed the area/UX label Dec 3, 2019
@deviantony deviantony added this to the next milestone Dec 3, 2019
@deviantony deviantony added the priority/high Core team priority label Dec 3, 2019
@xAt0mZ
Copy link
Member

xAt0mZ commented Dec 3, 2019

Images are already filtered to be unique across the swarm. The problem we have here is that the ID of images (so the version for each node) is not necessary the same.
2019-12-03-150325_1920x1080_scrot
As we only display the tag we are seeing duplicates, but they are not.

I can push a fix where all tags are always unique regardless of the source image ID and the origin of the image.

Tho it can lead to weird issues:

  • deploying a service with nginx:latest with different images on every node can lead to an unknown behaviour (can't recall if we are making a force pull in this situation)
  • in a multinode env, creating a container without force pull can lead to images not existing on the target node : we may need to add an additional filter to list only the images existing on the target node

@deviantony
Copy link
Member

@xAt0mZ yes, please filter on unique image names.

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

Successfully merging a pull request may close this issue.

2 participants