Can´t start workspace in multiuser mode
See original GitHub issueThen of install and run eclipse che in multiuser mode, i can create a new workspace but i cant run it.
I run a server in a vm virtualbox with the next command:
docker run -it -v /var/run/docker.sock:/var/run/docker.sock -v /data/example:/data -e CHE_PORT=9000 -e CHE_CONTAINERT=example -e CHE_MULTIUSER=true eclipse/che start
Then i create a new workspace for the user, but when i run it this error appears:
Could not start workspace wksp-q0qx. Reason: Start of environment ‘default’ failed. Error: Error response from docker API, status: 404, message: No such network: che_che-network
OS and version:
Ubuntu 16.04.3
Issue Analytics
- State:
- Created 6 years ago
- Comments:10 (2 by maintainers)
Top Results From Across the Web
Administer WorkSpace users - AWS Documentation
Each WorkSpace is assigned to a single user and cannot be shared by multiple users. By default, only one WorkSpace per user per...
Read more >QuickBooks Multi – User Mode Error [- 6123,0]
QuickBooks Multi – User Mode Error [- 6123,0] · 1) Reboot the system and then restart QuickBooks. · 2) Go to File>Utilities>Stop Hosting...
Read more >Multiuser mode - Tosca - Tricentis
Multiuser mode. Tosca provides access management for elements of the common repository. This prevents access conflicts irrespective of the number of users.
Read more >How to set up multi-user mode in the OneSoil mobile and web ...
Multi-user mode has 4 roles: owner, administrator, editor, and viewer. The Owner: Has access to all information in the workspace. Can edit, ...
Read more >Multi-User Editing Overview - Unreal Engine Documentation
While inside a session workspace, each user can interact with the Project ... You can also choose to have the Multi-User Editing system...
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
OK, found what causes the issue.
@riuvshin please take a look:
Here we instruct Che server what docker network to use:
https://github.com/eclipse/che/blob/ee01b2998feac77f3408a80ee6e5386e09e23b9f/dockerfiles/init/modules/che/templates/che.env.erb#L27
When CHE_PORT is set, docker networks are created with a prefix which is
che$port
As a result, networks are created according to this naming pattern and a non existent network is passed to server’s java opts.
@alber7rp as a workaround you can override
CHE_DOCKER_NETWORK=
I will take a look on this one