search

labring / sealos

Sealos is a production-ready Kubernetes distribution. You can run any Docker image on sealos, start high availability databases like mysql/pgsql/redis/mongo, develop applications using any Programming language.
https://cloud.sealos.io
Apache License 2.0
13.84k stars 2.07k forks source link

Failed to transfer image during installation #4770

Closed yulinor closed 3 months ago

yulinor commented 3 months ago

Sealos Version

v4.3.7 v5.0.0-beta

How to reproduce the bug?

OS openeuler 24.03 LTS

253 作为外部控制机，其他主机作为真实master，如101

sealos gen labring/kubernetes:v1.29.5-4.3.7 labring/helm:v3.14.0 labring/metrics-server:v0.6.4 --masters 192.168.3.101,192.168.3.102,192.168.3.103  ....
sealos apply -f  ...
warn failed to copy image 127.0.0.1:46879/kube-apiserver:v1.29.5: trying to reuse blob sha256:b2ce0e0660777651a7a188ae1128acc61d01aca10a035a8b1faa2cdd8bbf0785 at destination: pinging container registry 192.168.3.101:5050: received unexpected HTTP status: 502 Bad Gateway

sealos 同步镜像至101（master0)的5050 registry，但是registry启动 http 5000/ debug 5001 ，所以始终提示 502 Bad Gateway

What is the expected behavior?

No response

What do you see instead?

No response

Operating environment

- Sealos version:  v4.3.7
- Docker version: no
- Kubernetes version:  labring/kubernetes:v1.29.5-4.3.7
- Operating system: openeuler 2403
- Runtime environment: no
- Cluster size: no 
- Additional information: no

Additional information

No response

yulinor commented 3 months ago

初步解决了，原因是proxy没有放行内网网段导致无法连接到master0

sealos-ci-robot commented 3 months ago

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

The problem was initially solved. The reason was that the proxy did not release the intranet segment and therefore could not connect to master0.