Che mount broken in Che6
See original GitHub issueThere are multiple problems:
- Root user being used to default
let user : string = "root";
- Error in extracting the url
let address: Array<string> = sshAgentServer.getUrl().replace("/", "").split(":");
- docker syntax being used without any multi-user flags. It’s fixed for che actions but not for che mount that calls che actions commands.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:7 (4 by maintainers)
Top Results From Across the Web
ITC Grand Chola, Chennai, a Luxury Collection Hotel
With its awe-inspiring size and grandeur, ITC Grand Chola is a veritable destination unto itself. Located in the heart of Chennai the hotel...
Read more >Body mount repair - The Build - YouTube
During this episode of The Build, the team attacks a rusty body mount with two different metal cutters, the whiz wheel and a...
Read more >Chennai Metro - Wikipedia
The Chennai Metro is a rapid transit system serving the city of Chennai, Tamil Nadu, India. It is the 4th longest metro system...
Read more >Online Appointment - Sankara Nethralaya
8, G. S. T. Road, St. Thomas Mount, Chennai - 600 016 ... This will help us fix an appointment with the appropriate...
Read more >Find cheap flights from San Francisco to Chennai - SFO - Kayak
Find flights to Chennai from $458. Fly from San Francisco on Air France, Air India, Delta and more. Search for Chennai flights on...
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
@davidwindell That looks great, I did see it earlier but preferred to use built in Che functionality where possible. Can I ask why you made that instead of using, improving or fixing the sync functionality within Che?
I do find it a bit odd Che sync seems to have been broken for 8+ months when the issue seems fairly simple to fix (from looking at other issues), it’s local IDE selling point is mentioned on the home page as a “core capability” so I’m wondering why it’s been left broken for so long, or if I’m missing part of the puzzle as a new (ish) user.
I’ve just given che-sync a go, and getting an unable to authenticate with server. We are running Che multi user via Docker on a DO box with keycloak on 5050, Che on 8080 - looking at entrypoint.sh it looks like it’s compatible with that setup. I’ll investigate further and post on your repository if I find an issue, rather than clutter this thread with non Che stuff. Thanks!
@jakgsl you might be interested in our https://github.com/outeredge/che-sync tool - our team of 5 uses it for all our projects