Can not start a workspace: configured storage type not supported
See original GitHub issueDescribe the bug
I get an error at starting workspace: Failed to open the workspace. Error provisioning storage: configured storage type not supported
Che version
next (development version)
Steps to reproduce
- Start a minikube
- Go to dashboard
- Go to
Create workspace
- Put
https://github.com/che-incubator/che-code
to theGit Repo URL
field Create and Open
button
Expected behavior
The workspace has started successfully
Runtime
minikube
Screenshots
Installation method
chectl/next
Environment
macOS
Eclipse Che Logs
No response
Additional context
No response
Issue Analytics
- State:
- Created a year ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Amazon WorkSpaces Now Supports Configurable Storage ...
Today, Amazon WorkSpaces is making two new features available. First, you can now configure how much storage your WorkSpaces get when you ...
Read more >Installation issues - Google Workspace Admin Help
This issue is typically caused by installing Exchange Server management tools, which includes an incompatible version of MAPI32.DLL. To fix the issue, uninstall ......
Read more >00264: Branch versioned dataset, <value>, is not supported ...
Error 00264 : Branch versioned dataset, <value>, is not supported from a versioned workspace when the service is editable.
Read more >Chapter 4. Known issues Red Hat OpenShift Dev Spaces 3.0
Currently, the per-workspace workspace storage strategy is not supported due to the change to the DevWorkspace engine. With migration from CodeReady Workspaces ......
Read more >Amazon WorkSpaces - FAQs – Amazon Web Services
The instance store is ideal for temporary content like caches and buffers, because the data stored in instance store volumes is not persistent...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@ibuziuk and I discussed that chectl needs to use an updated image of DWO, and chectl nightly should probably use the nightly build of DWO. cc: @tolusha
I was able to reproduce this issue, looking into it.