Skip to content

Feature Request: Autodiscovery / support private registry which is running on non default https port (443) but e.g. 5000 #6862

@allroundtechie

Description

@allroundtechie

Is your feature request related to a problem?

Hi there,

I don't know if this is basically a feature request but because I did not found anything related in the documentation and also in the issues on GitHub I will give it a shot.

I tried to move my private registry which hosts all the docker images to another port than 443.
In this case it was port 5000 which is also the default port for the docker registry (https://hub.docker.com/_/registry)
I use Nomad so everything is defined in a HCL file like:

image = "registry.service.consul/container/redis:8.4.0"

This works like a charm with updatecli autodiscovery, it detects the image perfectly.
But when I move the port of the registry to 5000

image = "registry.service.consul:5000/container/redis:8.4.0"

updatecli does not find anything:

NOMAD
======
No source spec detected
Manifest detected: 0
---
=> Total manifest detected: 0
nothing detected

My question here and maybe as a result a feature request: Does updatecli in autodiscovery not handle different ports than 443 for registries (not implemented or by choice)?
Thanks in advance and also thanks for this awesome time saver tool!!!

Solution you'd like

No response

Alternatives you've considered

No response

Anything else?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingresource-dockerResource of kind Docker Imageresource-dockerfileResource of kind Dockerfile

    Type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions