Container name incorrect when links are used.

[MicahZoltu]

Bug description
When linking container foo to container bar, the name displayed for container bar changes to be foo/bar. This does not align with what shows up in docker container list, nor is it a desirable behavior (for me).

Expected behavior
When I name a container foo, I expect to see it listed with then name foo in the container list.

Steps to reproduce the issue:

Steps to reproduce the behavior:

1. docker container run -d --name foo httpd:alpine
2. docker container run -d --name bar --link foo httpd:alpine
3. Look at container list and notice that foo is named bar/foo.

Technical details:

• Portainer version: 1.19.1
• Docker version (managed by Portainer): 18.06.1-ce
• Platform (windows/linux): Linux
• Command used to start Portainer: docker run -d --name portainer --restart always --mount='type=bind,source=/var/run/docker.sock,dst=/var/run/docker.sock' --mount 'source=portainer,dst=/data' portainer/portainer
• Browser: Edge

[francescbassas]

+1

[openhoat]

+1

[thomashilzendegen]

Portainer's JSON API is returning a Names array, containing the "wrong" name at first place:

"Names": ["/bar/foo", "/foo"]

[ghost]

Reproduced on 1.23.2

[griou]

Hello, I can still reproduce this issue and it has boring side effects : if you need to stop container to set some environment variables, you can't Duplicate/Edit the containers (having error with the container name because it's using the link and not the container name) and when you use Recreate you can't keep the link beetween the containers. Could you help fix this issue ? Thanks for any help.

[xventil]

same issue for me also running portainer 1.24

[driesvandamme]

Same issue here. It makes managing the containers (with Synology Docker application) a mess.

[MarcOrfilaCarreras]

Same issue using Portainer Community Edition with the version 2.15.0. Using the linux-arm64 image.