[ws-manager] stuck in stopping: "container with exit code 1" ("cannot connect to daemon") #5271
Labels
component: ws-manager
groundwork: awaiting deployment
priority: highest (user impact)
Directly user impacting
team: workspace
Issue belongs to the Workspace team
type: bug
Something isn't working
Bug description
This bug very likely hid behind a mitigation for another problem for some time. We don't properly stop workspaces when supervisor "cannot connect to daemon" and the container exits with code "1".
Event trace: https://www.notion.so/gitpod/Task-Force-ws-daemon-restarts-b659846b2fad457eb55ec91c61d82eba#e516e9f48b584e2e8076eb3976b5f55b
Log query to identify cases: https://cloudlogging.app.goo.gl/ENj21hoLRyey9fYB7
DB query to (very likely) identify cases:
resulting instanceIds (mostly - but not exclusively - prebuilds) :
Steps to reproduce
see above
Expected behavior
No response
Example repository
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: