You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the dogfooding cluster, I configured the SSH keys to use in my workspaces as described here. With the secret configured, my workspaces were constantly failing to start with the error: Error creating DevWorkspace deployment: Init Container che-code-injector has state CreateContainerError.
che-bot
added
the
status/need-triage
An issue that needs to be prioritized by the curator responsible for the triage. See https://github.
label
Oct 23, 2023
I tested this briefly with Che next and wasn't able to reproduce the issue -- I suspect it may be occurring due to a file mounting collision (e.g. two secrets that mount the same file name to the same path, ssh_config for example) and have opened devfile/devworkspace-operator#1194 preemptively (since it seems like DWO is not currently checking for such collisions)
@amisevsk thank you for the hint! I went through the list of secrets and found another SSH key secret created a long time ago. Removing the extra one secret resolved the issue.
Describe the bug
On the dogfooding cluster, I configured the SSH keys to use in my workspaces as described here. With the secret configured, my workspaces were constantly failing to start with the error:
Error creating DevWorkspace deployment: Init Container che-code-injector has state CreateContainerError
.Removing the secret eliminates the problem.
Steps to reproduce
Expected behavior
Workspace is running.
Screenshots
Progress
Events
The text was updated successfully, but these errors were encountered: