添加链接

注册登录

link管理

链接快照平台

输入网页链接，自动生成快照
标签化管理网页链接

Troubleshooting Gitpod Self-Hosted

⚠️ Deprecated Content

The content of this page assumes you are using Helm, which is now deprecated. Please use the Installer instead.

This section should solve all errors that might come up during installation of Gitpod.

1. `ws-daemon` is stuck in `Init: 0/1`

kubectl describe pod ws-daemon-... gives: MountVolume.SetUp failed for volume "node-fs1" : hostPath type check failed: /run/containerd/io.containerd.runtime.v1.linux/k8s.io is not a directory

Solution

ssh onto the node, mount | grep rootfs and find the directory where your containers are stored. Common paths are:
- /run/containerd/io.containerd.runtime.v1.linux/k8s.io
- /run/containerd/io.containerd.runtime.v1.linux/moby
- /run/containerd/io.containerd.runtime.v2.task/k8s.io

Merge the following into your values.custom.yaml :


     
      
       Example: For
       
        k3s
       
       a common configuration looks like this:
      
     
     
      language:


   
    2.
    
     helm install
    
    fails with: “minio access key is required, please add a value to your values.yaml”
    
     
     
    
   
   
    Since
    
     0.7.0
    
    minio requires custom credentials to be configured.
   
   
    Solution
    
     
     
    
   
   
    
     Follow the
     
      Upgrade Guide
     
     .
    
   
   
    3. After upgrade, the
    
     minio
    
    Pod is stuck in
    
     ContainerCreating
    
    
     
     
    
   
   
    This is caused by a bug in the minio Helm chart which blocks itself on updates.
   
   
    Solution
    
     
     
    
   
   
    
     
      
       kubectl scale deployments/minio --replicas=0
      
     
    
    
     
      
       kubectl scale deployments/minio --replicas=1
      
     
    
    
     
      Wait until the pod comes up.
     
    
   
   
    3.
    
     agent-smith
    
    daemonset fails in deployment
    
     
     
    
   
   
    In the v0.10.0 release
    
     agent-smith
    
    is
    
     incorrectly enabled
    
    in Gitpod Self-Hosted.
   
   
    Solution
    
     
     
    
   
   
    Add the following to your
    
     values.yaml
    
    file to disable agent-smith:
   
   
    language:

推荐文章

爽快的盒饭 · 火焰之纹章主角大联盟官网在哪下载最新官方下载安装地址_火焰之纹章主角大联盟手游_光环助手网页版

1 月前

安静的包子 · 俄罗斯电影史-大连外国语大学-俄语中心

3 月前

被表白的盒饭 · 市经济信息化委关于开展2024年度上海市工业通信业节能减排和合同能源管理专项资金项目申报工作的通知

5 月前

文质彬彬的酸菜鱼 · 我的荣耀V30手机在拨号中输入*#*#6130#*#*无反应，请问是什么原因，怎么解决 - CSDN文库

7 月前

悲伤的鸭蛋 · 5个炫酷的python 数据可视化工具，你都用过吗？ - 知乎

9 月前

Link管理 · 51好读 · Sov5搜索 · 小百科

link管理 - 链接快照平台

Troubleshooting Gitpod Self-Hosted

1. `ws-daemon` is stuck in `Init: 0/1`

Solution

2. `helm install` fails with: “minio access key is required, please add a value to your values.yaml”

Solution

3. After upgrade, the `minio` Pod is stuck in `ContainerCreating`

Solution

3. `agent-smith` daemonset fails in deployment

Solution

4. Workspaces stopping once container image downloaded

Solution

5. Create workspace results in `7 PERMISSION_DENIED: cannot resolve workspace image` error

Solution

Troubleshooting Gitpod Self-Hosted

1. ws-daemon is stuck in Init: 0/1

Solution

2. helm install fails with: “minio access key is required, please add a value to your values.yaml”

Solution

3. After upgrade, the minio Pod is stuck in ContainerCreating

Solution

3. agent-smith daemonset fails in deployment

Solution

4. Workspaces stopping once container image downloaded

Solution

5. Create workspace results in 7 PERMISSION_DENIED: cannot resolve workspace image error

Solution

1. `ws-daemon` is stuck in `Init: 0/1`

2. `helm install` fails with: “minio access key is required, please add a value to your values.yaml”

3. After upgrade, the `minio` Pod is stuck in `ContainerCreating`

3. `agent-smith` daemonset fails in deployment

5. Create workspace results in `7 PERMISSION_DENIED: cannot resolve workspace image` error