Skip to content

[self-hosted] Workspace initialisation fails with error on PrepareForUserNS with moby #3909

Closed
@pavan-tri

Description

@pavan-tri

Bug description

When the workspace starts, the ws-daemon/workspace-kit is trying to initialize ring0 and makes a GRPC call PrepareForUserNS. This call times out, leading it to stopping of intialization. WS go into "stopped" state.

nodeRoot was changed to "moby" as per troubleshooting guide for Self-hosted.

First Observation: Containerd wrapper is having a hardcoded namespace ( k8s.io Link) . When I changed the nodeRoot to moby, the underlying containerd runtime is expecting a "moby" name space. This is leading to no Container ID found error messages

Second Observation: Containerd wrapper also expects c.Labels to have map entries like "io.kubernetes.pod.name". With moby namespace the only map entry available is "com.docker/engine.bundle.path"

Steps to reproduce

Env Details:

AWS - EKS 1.16
Ubuntu 18.04 AMI
Containerd: 1.3.3-0ubuntu1~18.04.4

ws-daemon config:

workspaceSizeLimit: "5g"
nodeRoots:

  • /var/lib
  • /run/containerd/io.containerd.runtime.v1.linux/moby

Expected behavior

WorkSpace should start.

Example repository

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions