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

BUG: unable to install sealos-cloud by one step. install script #4610

Closed perlinson closed 1 month ago

perlinson commented 6 months ago

Sealos Version

v4.3.7

How to reproduce the bug?

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

What is the expected behavior?

No response

What do you see instead?

kubectl apply -f manifests/deploy.yaml -f manifests/rbac.yaml -f manifests/ingress.yaml serviceaccount/desktop-frontend created service/desktop-frontend created configmap/desktop-frontend-config created deployment.apps/desktop-frontend created clusterrole.rbac.authorization.k8s.io/auth-system-manager-role created clusterrolebinding.rbac.authorization.k8s.io/desktop-user-editor-role-binding created clusterrolebinding.rbac.authorization.k8s.io/desktop-operationrequest-editor-role-binding created clusterrolebinding.rbac.authorization.k8s.io/desktop-deleterequest-editor-role-binding created role.rbac.authorization.k8s.io/recharge-gift-cm-reader created rolebinding.rbac.authorization.k8s.io/recharge-gift-cm-reader-rolebinding created clusterrole.rbac.authorization.k8s.io/account-editor-role created clusterrolebinding.rbac.authorization.k8s.io/desktop-account-editor-role-binding created Warning: annotation "kubernetes.io/ingress.class" is deprecated, please use 'spec.ingressClassName' instead Error from server (InternalError): error when creating "manifests/ingress.yaml": Internal error occurred: failed calling webhook "validate.nginx.ingress.kubernetes.io": failed to call webhook: Post "https://ingress-nginx-controller-admission.ingress-nginx.svc:443/networking/v1/ingresses?timeout=10s": no endpoints available for service "ingress-nginx-controller-admission" Error: exit status 1 Error: exit status 1

Operating environment

SealosVersion:
  buildDate: "2023-10-30T16:19:05Z"
  compiler: gc
  gitCommit: f39b2339
  gitVersion: 4.3.7
  goVersion: go1.20.10
  platform: linux/amd64

Additional information

是用的家庭宽带,系统是 ubuntu 22.04 内存11g

codecoron commented 5 months ago

I also meet this issue sealos pull -q registry.cn-shanghai.aliyuncs.com/labring/kubeblocks-redis:v0.8.2

Error: initializing source docker://registry.cn-shanghai.aliyuncs.com/labring/kubeblocks-redis:v0.8.2: reading manifest v0.8.2 in registry.cn-shanghai.aliyuncs.com/labring/kubeblocks-redis: requested access to the resource is denied

bxy4543 commented 5 months ago

kubectl get pod -A execute the command to check whether the basic components are started successfully.

stale[bot] commented 3 months ago

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