Port rewriting when adding a registry about admiral HOT 5 CLOSED

@It4lik looks like you are running your registry (Apache reverse proxy) on port 443. However in the web UI of Admiral, if you don't specify a port, it defaults to 5000, as it is the common docker registry port. But yes, you are right to think that it will default to 443 for https and 80 for http, so we can improve the UI to hint the default port.
Can you try to register your registry as
https://my.private.domain:443

Thanks

from admiral.

I tried, and that works with https://my.private.domain:443 :)

Mmmh "funny" thing, with nothing provided (and then Admiral puts 5000 as a default behaviour), and an imported docker-compose.yml as a template, I didn't got any problem to run my containers.
So the problem only arises when trying to run a container alone, not when using a template.

from admiral.

I believe although the error message is displaying the whole url with the added port, this is common confusion for users. We need to add the functionality when a user enters the ip/hostname of registry, if the port is not specified, on focus change, the UI should add the default port. Some other hints or suggestions should show the default ports and default schema as well.

@It4lik, do you have the whole path of the registry before the image in the docker-compose.yaml. This might explain why it is working from docker-compose.yaml.

from admiral.

Yep I have the whole path of my registry in the "image" section in my compose.yaml.

I think that adding default port while losing the focus is a good idea :)

from admiral.

Commit d7a89cf addresses the problem:

• changed default ports to 80/443 for docker and registry hosts
• added tooltip hints about default scheme and port for registry and
  docker host addresses
• changed address fields to auto-populate missing scheme and port
  when they lose focus

from admiral.