-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[container-runtime] if workspace pod has more than 2 containers, ws-daemon ExtractCGroupPathFromContainer fails #14103
Comments
I don't think the error you are seeing in the log is the cause of the socket not being available. That comes from the process priority cgroup plugin which should not affect startup. |
@Furisto if I remove init container then it works. So it is definitely something to do with the second container in the pod. |
It may relates to this issue. I'm fixing. |
Bug description
In this PR I am adding init container (when using PVC) to workspace pod: #14096
It causes workspace to fail to start up as it times out waiting for daemon.sock to appear.
Looking at ws-daemon logs, it errors out with:
For some reason, something appears to be not working as we are expecting it to when there is more then one container in workspace pod.
I double check container ID in
gitpod/components/ws-daemon/pkg/container/containerd.go
Line 184 in a0f3e3d
workspace
container and uses it to create cgroup path.Here is full log (with additional debug output that I added):
Steps to reproduce
Use preview env from this PR: #14096
Enable PVC.
Try to open any workspace.
Workspace affected
No response
Expected behavior
No response
Example repository
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: