Che: Che mount broken in Che6

Created on 2 Feb 2018 · 6Comments · Source: eclipse/che

There 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.

kinbug severitP2

Source

ghost

👍2

All 6 comments

@skabashnyuk : Could your team give a look at this issue ?

slemeur on 12 Feb 2018

Is this issue being looked at in the near future? Our team is having a few problems with the built in IDE; and for some projects we need a fully fledged local IDE so sync is essential for us. We could have a look at fixing it as it's a blocking issue for us, it seems it could be a quite simple fix as it was already fixed for list workspaces?

jakgsl on 11 Oct 2018

@jakgsl you might be interested in our https://github.com/outeredge/che-sync tool - our team of 5 uses it for all our projects

davidwindell on 11 Oct 2018

👍1

@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 on 11 Oct 2018

👍1

@davidwindell i dont get auth problems as @jakgsl, but the starting of the workspace fails.

@jakgsl did you found any workaround for mounting?