Image repository/tag not shown for images from stack deploy

[Duvel]

Description

If you deploy services with docker stack, the images don't get tags and the tag column in the list of images will be empty.

Steps to reproduce the issue:

1. deploy a stack
2. check tags for the images
3. observe image tag is empty

[Duvel]

Example stack file:

version: "3.2"
services:
  traefik:
    image: traefik:v1.4.2
    command: --web --docker.swarmmode --docker.domain=docker.localhost --logLevel=DEBUG --docker.watch
    ports:
      - "80:80"
      - "8080:8080"
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - /dev/null:/traefik.toml
    networks:
      - traefik
    deploy:
      placement:
        constraints: [node.role == manager]

networks: 
  traefik:
    attachable: true

[Duvel]

[ulm0]

This is related to Swarm itself, it uses the hash generated instead of the tag, so Swarm can identify the differences across images with same tag but built and pushed in different dates, this is a nice use-case when using :latest images

[deviantony]

Sorry for the late update.

From what I can see in that specific use case, the output of the docker images command is the following:

traefik             <none>              2e7af90a3e22        6 weeks ago         45.6MB

Not sure that we want to display the tag traefik:<none> inside the images list as it's sort of a confusing tag...

Maybe just tag it as traefik ?

cc @ncresswell

[Duvel]

Would be fine for me, I just need some identification in the images list to keep them apart.

[ibnesayeed]

We can perhaps read the image name and tag from the stack file and tag the image accordingly. If there is an explicit tag then use that otherwise use latest (that would be the expected behavior).

[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.