BUG: brief description of the bug

[einnse]

Sealos Version

v5.0.0

How to reproduce the bug?

curl -sfL https://mirror.ghproxy.com/https://raw.githubusercontent.com/labring/sealos/v5.0.0/scripts/cloud/install.sh -o /tmp/install.sh && bash /tmp/install.sh \
  --cloud-version=v5.0.0 \
  --image-registry=registry.cn-shanghai.aliyuncs.com --zh \
  --proxy-prefix=https://mirror.ghproxy.com

program aborted Error: exit status 2
infracreate-registry.cn-zhangjiakou.cr.aliyuncs.com/apecloud/snapshot-controller:v6.2.1 pull image 403 Forbidden

What is the expected behavior?

No response

What do you see instead?

addon.extensions.kubeblocks.io/snapshot-controller enabled
secret/additional-scrape-configs created
vmagent.operator.victoriametrics.com/victoria-metrics-k8s-stack patched
deployment.apps/vmagent-victoria-metrics-k8s-stack restarted
正在修改 Ingress-nginx-controller 的容忍度, 以允许它在主节点上运行.
configmap/ingress-nginx-controller patched
daemonset.apps/ingress-nginx-controller patched
daemonset.apps/ingress-nginx-controller patched
daemonset.apps/ingress-nginx-controller patched
正在安装 Sealos Cloud.
2024-08-03T23:03:59 info start to install app in this cluster
2024-08-03T23:03:59 info Executing SyncStatusAndCheck Pipeline in InstallProcessor
2024-08-03T23:03:59 info Executing ConfirmOverrideApps Pipeline in InstallProcessor
2024-08-03T23:03:59 info Executing PreProcess Pipeline in InstallProcessor
2024-08-03T23:03:59 info Executing pipeline MountRootfs in InstallProcessor.
2024-08-03T23:04:03 info render /var/lib/sealos/data/default/applications/default-hyll1ffo/workdir/etc/sealos/.env from /var/lib/sealos/data/default/applications/default-hyll1ffo/workdir/etc/sealos/.env.tmpl completed
2024-08-03T23:04:03 info render /var/lib/sealos/data/default/applications/default-hyll1ffo/workdir/manifests/mock-cert.yaml from /var/lib/sealos/data/default/applications/default-hyll1ffo/workdir/manifests/mock-cert.yaml.tmpl completed
2024-08-03T23:04:03 info render /var/lib/sealos/data/default/applications/default-hyll1ffo/workdir/manifests/mongodb.yaml from /var/lib/sealos/data/default/applications/default-hyll1ffo/workdir/manifests/mongodb.yaml.tmpl completed
2024-08-03T23:04:03 info Executing pipeline MirrorRegistry in InstallProcessor.
2024-08-03T23:04:03 info Executing UpgradeIfNeed Pipeline in InstallProcessor
etc/sealos/.env: line 1: syntax error near unexpected token `newline'
Error: exit status 2

Operating environment

- Sealos version: v5.0.0.
- Docker version:
- Kubernetes version: v1.29.7
- Operating system: Rocky Linux 9.2
- Runtime environment: virtual machine (vmware, 20G memory, 12 core cpu, 500G storage)
- Cluster size: 1master,1node
- Additional information:

Additional information

[root@sealos-master ~]# kubectl get nodes -o wide
NAME            STATUS   ROLES           AGE   VERSION   INTERNAL-IP      EXTERNAL-IP   OS-IMAGE                      KERNEL-VERSION                 CONTAINER-RUNTIME
sealos-master   Ready    control-plane   46m   v1.29.7   192.168.50.68    <none>        Rocky Linux 9.2 (Blue Onyx)   5.14.0-284.11.1.el9_2.x86_64   containerd://1.7.20
sealos-node     Ready    <none>          46m   v1.29.7   192.168.50.226   <none>        Rocky Linux 9.2 (Blue Onyx)   5.14.0-284.11.1.el9_2.x86_64   containerd://1.7.20

kb-addon-snapshot-controller

  Normal   Scheduled  49s                default-scheduler  Successfully assigned kb-system/kb-addon-snapshot-controller-7bc7cf9dbf-vgcqg to sealos-node                                                                             │
│   Normal   BackOff    18s (x2 over 48s)  kubelet            Back-off pulling image "infracreate-registry.cn-zhangjiakou.cr.aliyuncs.com/apecloud/snapshot-controller:v6.2.1"                                                         │
│   Warning  Failed     18s (x2 over 48s)  kubelet            Error: ImagePullBackOff                                                                                                                                                  │
│   Normal   Pulling    5s (x3 over 49s)   kubelet            Pulling image "infracreate-registry.cn-zhangjiakou.cr.aliyuncs.com/apecloud/snapshot-controller:v6.2.1"                                                                  │
│   Warning  Failed     4s (x3 over 49s)   kubelet            Failed to pull image "infracreate-registry.cn-zhangjiakou.cr.aliyuncs.com/apecloud/snapshot-controller:v6.2.1": failed to pull and unpack image "infracreate-registry.cn │
│ -zhangjiakou.cr.aliyuncs.com/apecloud/snapshot-controller:v6.2.1": failed to copy: httpReadSeeker: failed open: unexpected status code https://infracreate-registry.cn-zhangjiakou.cr.aliyuncs.com/v2/apecloud/snapshot-controller/b │
│ lobs/sha256:1ef6c138bd5f2ac45f7b4ee54db0e513efad8576909ae9829ba649fb4b067388: 403 Forbidden                                                                                                                                          │
│   Warning  Failed     4s (x3 over 49s)   kubelet            Error: ErrImagePull   

[bxy4543]

@wallyxjh

[sealos-ci-robot]

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

---

@wallyxjh

[hanxianzhai]

遇到了同样的问题。

[sealos-ci-robot]

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

---

Encountered the same problem.

[stale]

This issue has been automatically closed because we haven't heard back for more than 60 days, please reopen this issue if necessary.