Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can not do CLI mount #2123

Closed
thyeun opened this issue Aug 15, 2016 · 39 comments
Closed

Can not do CLI mount #2123

thyeun opened this issue Aug 15, 2016 · 39 comments
Assignees
Labels
kind/bug Outline of a bug - must adhere to the bug report template. kind/question Questions that haven't been identified as being feature requests or bugs.

Comments

@thyeun
Copy link

thyeun commented Aug 15, 2016

Not possible to done the Che mount, it keep on given an error path does not exist, as you can see from the picture below. (i have the correct ws-ssh-port, and "mount" folder)

OS : windows 10 build 10240
Che Version : 4.6.2

s9

@ghost ghost added the kind/question Questions that haven't been identified as being feature requests or bugs. label Aug 15, 2016
@ghost
Copy link

ghost commented Aug 15, 2016

@thyeun what if you provide this path as c/users/thomas/mount? Does it make any difference.

@TylerJewell
Copy link

TylerJewell commented Aug 15, 2016

We convert directory names from the c: format to the one you describe, Eugene. The issue is virtualbox does not allow the directory provided by @thyuen to be mounted. It is a virtualbox problem.

@thyeun
Copy link
Author

thyeun commented Aug 15, 2016

@TylerJewell and @eivantsov, here goes all the try as show from the below pictures, but non of it success, but one of them have a different error (can not enable tty mode)

s11

@ghost
Copy link

ghost commented Aug 15, 2016

@thyeun can you ssh into a machine?

docker-machine ssh $machineName and check if the path exist?

@thyeun
Copy link
Author

thyeun commented Aug 15, 2016

@eivantsov , yes, show at the below picture, but i can not access into c/users/

s12

s13

@thyeun
Copy link
Author

thyeun commented Aug 15, 2016

sorry @eivantsov , i typo mistake, i can access it

s14

@ghost
Copy link

ghost commented Aug 15, 2016

@thyeun do you see mount dir in there?

@thyeun
Copy link
Author

thyeun commented Aug 15, 2016

@eivantsov no, the last one is conf

@TylerJewell
Copy link

@thyeun - if you try to mount into the /conf directory, does that work? How did you create the /mount directory on your windows host?

@TylerJewell
Copy link

@thyeun - in reading virtualbox logs - there is also an issue with using capitalized letters and double slashes. Try `che mount //c/users/thomas/mount 32781' as a test. If this resolves it - we can do some magic on boot2docker to convert capitalized letters and add a slash.

moby/moby#12590

@thyeun
Copy link
Author

thyeun commented Aug 15, 2016

@TylerJewell the /conf directory is the magic for the customizes che.properties, for github.

ok, i will come back to you once i got the result.

@thyeun
Copy link
Author

thyeun commented Aug 15, 2016

@TylerJewell , `che mount //c/users/thomas/mount 32781' not possible, getting error message cannot enable tty mode on non tty input

@TylerJewell
Copy link

TylerJewell commented Aug 15, 2016

Ok! That means that the directory is passing for you now. That is a good thing. This mount ability is experimental - so we do expect unknown errors. Try the following.

First - get the IP address for inet from running:

docker run --rm --net host alpine sh -c "ip a show eth1"

then, run the following

docker run --rm -it --cap-add SYS_ADMIN \
                  --device /dev/fuse \
                  -v //c/users/thomas/mount:/mnthost \
                  codenvy/che-mount <ip-addr-from-above> <ws-ssh-port>

@thyeun
Copy link
Author

thyeun commented Aug 15, 2016

@TylerJewell Result as show below picture.

s15

@TylerJewell
Copy link

Ooops - bad syntax. I updated it - replace "docker_exec" with "docker"

@thyeun
Copy link
Author

thyeun commented Aug 15, 2016

@TylerJewell is ok, i figure it out, hahaha,

Result still same but with different error message, show at below picture

s16

@TylerJewell
Copy link

Ok - good - this means that there is flaw with che-mount. What happens if you replace "-it" with "-i"?

@thyeun
Copy link
Author

thyeun commented Aug 15, 2016

look better, pulling now, but abit slow!!!!

s17

will come back to you once it finish :)

@thyeun
Copy link
Author

thyeun commented Aug 15, 2016

@TylerJewell , the pulling process not moving at all. about 2 hours.

s18

@TylerJewell
Copy link

That is a problem with docker - should be really fast - it's less than 5mb. kill it and try again.

@thyeun
Copy link
Author

thyeun commented Aug 15, 2016

@TylerJewell Result as show from below picture, an error occur!!!

s19

@TylerJewell
Copy link

And without the double slash '//'? -- just a single slash '/'

@thyeun
Copy link
Author

thyeun commented Aug 15, 2016

Result '/ ' as picture below

s20

@TylerJewell
Copy link

Everything looks good - we'll have to leave this open until an engineer can run some tests with che mount for virtualbox. That will require a special environment.

@thyeun
Copy link
Author

thyeun commented Aug 15, 2016

ok......thanks

last question before i off, why everytimes i restart my PC and start again Che, my workspace will be gone?

and this docker run --rm -t -v //var/run/docker.sock:/var/run/docker.sock -e CHE_CONF_FOLDER=//c/Users/thomas/conf eclipse/che start, can not be working any more, i just manage to make the github auth working one time, after PC restart, it can not be working!!!

@TylerJewell
Copy link

YOu have the wrong variable :). You want CHE_DATA_FOLDER, not CHE_CONF_FOLDER. See: https://eclipse-che.readme.io/docs/usage-docker#environment-variables

@thyeun
Copy link
Author

thyeun commented Aug 15, 2016

ok... understand for the workspace issue need CHE_DATA_FOLDER.

but for a custom che.properties for github auth, it should be CHE_CONF_FOLDER, correct me if i'm wrong?

@TylerJewell
Copy link

Yeah, that is correct. CHE_CONF_FOLDER is where your che.properties file is.

If it's not working on PC restart - is it because your VM is not running in virtualbox? If the VM is running, did virtualbox properly mount the CHE_CONF_FOLDER again? So if you SSH into the vbox VM, is /c/users/thomas/conf/che.properties there?

@thyeun
Copy link
Author

thyeun commented Aug 15, 2016

Until here /c/users/thomas/conf from SSH into VM, can not find the file che.properties.

@thyeun
Copy link
Author

thyeun commented Aug 16, 2016

@TylerJewell abit different from #2122 ,

first show you the pictures SSH inside vboxVM, before restart PC, with the command line

docker run --rm -t -v //var/run/docker.sock:/var/run/docker.sock -e CHE_DATA_FOLDER=//c/Users/thomas/mount -e CHE_CONF_FOLDER=//c/Users/thomas/cong eclipse/che start

1st picture (for CHE_DATA_FOLDER), i got a "blank folder" inside IDE but SSH inside vboxVM, i can not find it

s21

2nd picture (for CHE_CONF_FOLDER), i create "cong folder" for custom che.properties. but SSH inside vboxVM i can not find the file.

s22

second show you the pictures SSH inside vboxVM after restart PC, with same command line

As from the picture below, you notice that the workspace that i created before restart PC, it gone.

s23

@TylerJewell
Copy link

@thyeun - I have been able to reproduce the issue on a local machine. Labeling it as a bug.

@TylerJewell TylerJewell added the kind/bug Outline of a bug - must adhere to the bug report template. label Aug 16, 2016
@TylerJewell
Copy link

@thyeun - in doing a variety of tests on Boot2Docker systems today, we found an issue with the CHE_DATA_FOLDER and CHE_LOCAL_BINARY commands for this particular system. I have submitted this pull request, which has improvements for the che-launcher container and the CLI which will fix the issues permanently.

Things should mostly work on windows as long as you keep your folders in c:\Users AND you do not have spaces in your folders. I was able to get spaces with folders to work on windows, but it will require a special syntax given some limitations in Docker.

#2119

@TylerJewell TylerJewell added this to the 4.7.0 milestone Aug 16, 2016
@TylerJewell TylerJewell self-assigned this Aug 16, 2016
@thyeun
Copy link
Author

thyeun commented Aug 17, 2016

@TylerJewell i just want to show you the spacing folder outcome also, but since you notice, than i keep the try for next version. hahaha

@bmicklea bmicklea changed the title Can not done CLI mount Can not do CLI mount Aug 18, 2016
@bmicklea bmicklea mentioned this issue Aug 18, 2016
89 tasks
@JamesDrummond
Copy link
Contributor

@TylerJewell Can you provide a status label?

@TylerJewell TylerJewell removed this from the 4.7.0 milestone Aug 22, 2016
@TylerJewell
Copy link

@JamesDrummond - I removed the milestone from this issue. It's not getting worked on currently - will not be until after #2119 is merged and resolved.

@TylerJewell
Copy link

@thyeun - we did a commit to master today that will fix the CHE_DATA_FOLDER issues for windows. We still will not support spaces in the folder names, though.

@TylerJewell
Copy link

@thyeun - closing this issue as a commit was done and it's in master now.

@JamesDrummond
Copy link
Contributor

@TylerJewell Will this be included in 4.7 or will we add it to the up coming 4.7.1?

@TylerJewell
Copy link

This is just a support ticket - so it doesn't get a milestone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Outline of a bug - must adhere to the bug report template. kind/question Questions that haven't been identified as being feature requests or bugs.
Projects
None yet
Development

No branches or pull requests

3 participants