Container Naming Confusion

[tohizma]

Is your feature request related to a problem? Please describe.

Portainer's naming for container is confusing, when I link a container to another container, it's name changed to something that doesn't meaningful, such as when netdata linked to nginx, nginx container name become NETDATA/NGINX that doesn't represent what this actual container is (in docker terms its read as [REPO-NAME]/[APP] )

And just curious why portainer choose port 9000 as default port?
Mentally this is conflict with php-fpm's port when quick searching for containers

Describe the solution you'd like

Portainer should respect what container's name is set in docker environment, we've choose each of container name carefully to prevents conflict and easy maintenance, so don't mess with it please

Could portainer default exposed port changed? At least in Docker official image, to (maybe) 9001 or another

Describe alternatives you've considered

If portainer need to display about container linkings, maybe a sub-title below container name, that states it is linked-to, or linked-by which container

Additional context

Another request is in Container Log screen, could you make Log Viewer Settings collapsible? It's eating too much space in small screen display

Thank you for this great software

[deviantony]

Hi there, could you show us some reproductions steps or screenshots? I'm not sure to understand what you're talking about for that "container link" feature.

Regarding the port number, it was decided arbitrarily in the past and has been used by Portainer for more than 3 years now, it's likely that it won't change to prevent issues with other users.

You can always expose that port to a different port number on your host(s).

[tohizma]

in that pic netdata/nginx is actualy nginx container, linked-by netdata
nginx/php-fpm is actualy php-fpm container, which is linked-by nginx

[deviantony]

@tohizma can you also screenshot / tell us how you created these containers?

[tohizma]

Please see my --name and --link params

Everything is fine in docker ps

[deviantony]

Ok, we might be using the raw response of the Docker API. This would require an inspection of the response of the containers/json HTTP request.

Tagging as an enhancement.