Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
perlinson opened this issue Mar 20, 2024 · 2 comments
Open

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

perlinson opened this issue Mar 20, 2024 · 2 comments
Labels
kind/bug Something isn't working

Comments

@perlinson
Copy link

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

@perlinson perlinson added the kind/bug Something isn't working label Mar 20, 2024
@codecoron
Copy link

codecoron commented Mar 31, 2024

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
Copy link
Member

bxy4543 commented Apr 10, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants