docker harbor goharbor/nginx-photon组件一直重启,harbor ip+port不通解决方法

docker harbor goharbor/nginx-photon组件一直重启,harbor ip+port不通解决方法

报错

docker重启之后发现goharbor/nginx-photon组件一直处于重启的状态,harbor使用的81端口也没有了,网页访问不了harbor

解决

经过排查发现可能是harbor网卡的问题,需要手动移除,

# cd /usr/local/harbor
# docker-compose down
# docker network  inspect harbor_harbor
[
    {
        "Name": "harbor_harbor",  #参数1
        "Id": "c3fd4485fc70ac39f304e1dc88e68c0292a6ed4d872bc246b47b8a1fee0c40f0",
        "Created": "2021-04-30T00:10:16.400151438+08:00",
        "Scope": "local",
        "Driver": "bridge",
        "EnableIPv6": false,
        "IPAM": {
            "Driver": "default",
            "Options": null,
            "Config": [
                {
                    "Subnet": "172.18.0.0/16",
                    "Gateway": "172.18.0.1"
                }
            ]
        },
        "Internal": false,
        "Attachable": true,
        "Ingress": false,
        "ConfigFrom": {
            "Network": ""
        },
        "ConfigOnly": false,
        "Containers": {
            "aa2c8463bd66f8c531e47bd81029dc4c5dde984909e0f55b56414bd4975acebe": {
                "Name": "nginx",    #参数2
                "EndpointID": "f47bbf14ced631b98270031e9b1a52e0f89789f4479b3f37c7855dd912d5119a",
                "MacAddress": "02:42:ac:12:00:02",
                "IPv4Address": "172.18.0.2/16",
                "IPv6Address": ""
            }
        },
        "Options": {},
        "Labels": {
            "com.docker.compose.network": "harbor",
            "com.docker.compose.project": "harbor",
            "com.docker.compose.version": "1.21.2"
        }
    }
]

# docker network disconnect -f harbor_harbor(参数1) nginx(参数2)
# docker-compose up -d

整体流程就是手动删除harbor_harbor网卡,重启harbor即可
在这里插入图片描述

我采用了方法三验证,输出[root@hmn0001 ycj]# curl -X GET http://172.25.26.250:5000/v2/_catalog {"repositories":["ai/gitea","aicc/aicc","aicc/aicc-site-controller","aicc/ainm","aicc/ainm_sidecar","airshipit/armada","baseimage/golang","beats/filebea","beats/filebeat","beats/filebeat-wolfi","bitnami/bitnami-shell","bitnami/elasticsearch","bitnami/kibana","bitnami/mariadb-galera","bitnami/minio","bitnami/nginx","bitnami/redis","bitnami/redis-sentinel","c1oudnative/eval-opencompass-arm","c1oudnative/evalscope-arm","c1oudnative/multi-arch-eval","calico/cni","calico/kube-controllers","calico/node","calico/pod2daemon-flexvol","cloud_native/model-hub","cloud_native/modelhub-backend","cloudnative/evalscope","cloudnative/model-evaluation","coredns","cuboss/golden-lion-api","cuboss/golden-lion-apps","cuboss/golden-lion-auth","cuboss/golden-lion-image","cuboss/vcuda","distroless/static","docker.io/memcached","docker.io/openstackhelm/ceph-config-helper","docker.io/openstackhelm/mariadb","docker.io/openstackhelm/rbd-provisioner","docker.io/openstackhelm/zookeeper","docker.io/rabbitmq","docker.io/release/stx-barbican","docker.io/release/stx-blackswan","docker.io/release/stx-cinder","docker.io/release/stx-designate","docker.io/release/stx-dimsagent","docker.io/release/stx-dimsmanager","docker.io/release/stx-glance","docker.io/release/stx-heat","docker.io/release/stx-ironic","docker.io/release/stx-keystone","docker.io/release/stx-nas","docker.io/release/stx-neutron","docker.io/release/stx-neutron-sdi","docker.io/release/stx-nova","docker.io/release/stx-octavia","docker.io/release/stx-openstackclients","docker.io/release/stx-sdi-agent","docker.io/release/stx-wnas","docker.io/starlingx/neutron-keepalived","docker.io/starlingx/neutron-nginx","docker.io/starlingx/neutron-telegraf","docker.io/starlingx/stx-libvirt","docker.io/starlingx/wnas-docker","dragonflyoss/busybox","dragonflyoss/dfdaemon","dragonflyoss/manager","dragonflyoss/mysql","dragonflyoss/openssl","dragonflyoss/redis","dragonflyoss/scheduler","dwinsdigitalservice/openstack-dashboard","ecr/cephfs-provisioner","ehpc/agent","ehpc/nginx","ehpc/oss-sync","ehpc/redis","ehpc/sshd","ehpc/ubuntu-sshd","ehpc/yum_centos","ehpc/yum_centos7","ehpc/yum_ule","elastic/elasticsearch","elastic/filebeat","elastic/kibana","gcc","gcr.io/google_containers/defaultbackend","gitea/bitnami-nginx","gitea/filebeat-httpout","gitea/gitea","gitea/nginx","gl-cluster-manager/gl-cluster-manager","goharbor/harbor-core","goharbor/harbor-db","goharbor/harbor-exporter","goharbor/harbor-jobservice","goharbor/harbor-log","goharbor/harbor-portal","goharbor/harbor-registryctl"]} 那我需要怎么修改我刚才的报错
03-15
<think>嗯,用户刚才执行了一个curl命令来获取Docker registry的仓库列表,现在遇到了报错,需要帮助解决。首先,我需要理解用户的具体问题是什么。用户提到他们用了“方法三”验证,但报错了,不过输出的结果看起来是正常的,列出了很多仓库。可能用户认为这个输出本身就是错误,或者实际有错误信息没有显示出来。 首先,我应该检查用户提供的命令和输出是否有问题。用户的命令是: ``` curl -X GET http://172.25.26.250:5000/v2/_catalog ``` 返回的JSON显示了很多仓库,状态码应该是200,但用户可能遇到了其他错误,比如权限问题、连接问题,或者返回的内容不符合预期。但根据输出,似乎请求是成功的,所以可能报错出现在其他步骤,而用户没有提供具体的错误信息。 接下来,用户需要修改刚才的报错,但问题描述不够详细。可能的报错原因包括:认证失败、registry版本不支持/_catalog端点、网络问题等。我需要引导用户提供更多信息,比如具体的错误提示、使用的Docker registry版本,以及是否配置了认证。 可能的解决步骤包括: 1. 检查网络连接是否正常,确保IP和端口正确。 2. 确认registry服务是否运行正常,查看服务日志。 3. 检查是否需要认证,添加用户名密码到curl命令。 4. 确认registry配置是否允许访问/_catalog端点,可能需要修改config.yml。 5. 验证registry版本是否支持该API。 用户可能需要补充具体的错误信息,以便更准确地诊断问题。同时,建议用户检查服务状态和配置文件,确保没有权限或配置上的限制。</think>根据你提供的输出,该命令成功获取了Docker Registry的镜像仓库列表。如果遇到报错,请先补充具体错误信息。以下是常见的排查方向: --- ### **一、先确认基础信息** 1. **检查IP和端口** - 确保 `172.25.26.250:5000` 是有效的Registry地址 - 执行 `ping 172.25.26.250` 验证网络连通性 - 执行 `telnet 172.25.26.250 5000` 验证端口是否开放 2. **检查Registry服务状态** 在Registry服务器上运行: ```bash systemctl status docker-registry # 假设使用systemd管理 docker ps | grep registry # 如果使用Docker容器运行 ``` --- ### **二、常见错误及修复** #### **场景1:认证失败(401 Unauthorized)** 如果返回类似 `401 UNAUTHORIZED`,需添加认证信息: ```bash curl -X GET -u username:password http://172.25.26.250:5000/v2/_catalog ``` #### **场景2:API不支持(404 Not Found)** 如果返回
评论 1
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值