harbor icon indicating copy to clipboard operation
harbor copied to clipboard

Run locally on predefined IP (eg 127.0.0.1)

Open kolesaev opened this issue 1 year ago • 3 comments

Is your feature request related to a problem? Please describe. While we are able to put Harbor behind a proxy we'd like to be able to run it on one interface, e.g. 127.0.0.1 for localhost

Describe the solution you'd like The best solution is to make it cofigurable via harbor.yml file

Describe the main design/architecture of your solution (nothing)

Describe the development plan you've considered (nothing)

Additional context Currently to move Harbor to one interface, we need to stop docker-compose manually after the installation, then edit docker-compose.yml file and up docker-compose again.

kolesaev avatar Feb 06 '24 11:02 kolesaev

Not sure if I understand your requirement, if you want Harbor to listen an a specific interface, you just check the IP of this interface and update the harbor.yml and install harbor.

stonezdj avatar Feb 19 '24 08:02 stonezdj

Not sure if I understand your requirement, if you want Harbor to listen an a specific interface, you just check the IP of this interface and update the harbor.yml and install harbor.

Hello, Sorry for my english, but it seems that you understood correctly. As i don't see a specific variable in harbor.yml, so i'd suppose that we are able to set it via http.port and https.port, like

https:
  port: 127.0.0.1:443

Am i right?

kolesaev avatar Feb 19 '24 16:02 kolesaev

Hello all,

my opinion: TS means the "bind" to the specific interface. You can give the harbor a host name in the harbor.yml, but it will be ignored.

# The IP address or hostname to access admin UI and registry service.
# DO NOT use localhost or 127.0.0.1, because Harbor needs to be accessed by external clients.
hostname: harbor-test.my.domain.org
sudo ss -tulpen
Netid State  Recv-Q Send-Q Local Address:Port  Peer Address:PortProcess
tcp   LISTEN 0      4096       127.0.0.1:1514       0.0.0.0:*    users:(("docker-proxy",pid=18021,fd=4))
tcp   LISTEN 0      4096         0.0.0.0:80         0.0.0.0:*    users:(("docker-proxy",pid=19022,fd=4))
tcp   LISTEN 0      128          0.0.0.0:22         0.0.0.0:*    users:(("sshd",pid=1945,fd=3))
tcp   LISTEN 0      100        127.0.0.1:25         0.0.0.0:*    users:(("master",pid=2028,fd=13))
tcp   LISTEN 0      4096         0.0.0.0:443        0.0.0.0:*    users:(("docker-proxy",pid=18974,fd=4))
tcp   LISTEN 0      4096         0.0.0.0:4443       0.0.0.0:*    users:(("docker-proxy",pid=18948,fd=4))
tcp   LISTEN 0      4096            [::]:80            [::]:*    users:(("docker-proxy",pid=19033,fd=4))
tcp   LISTEN 0      4096            [::]:443           [::]:*    users:(("docker-proxy",pid=18980,fd=4))
tcp   LISTEN 0      4096            [::]:4443          [::]:*    users:(("docker-proxy",pid=18956,fd=4))

Regards, temirg.

temirg avatar Feb 21 '24 14:02 temirg