Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Set variable CHE_DOCKER_MACHINE_HOST_EXTERNAL on Docker for Mac and Windows #11
Great job at CheConf16 today! Unfortunately, I still don't have Che fully working yet on my Mac.
I am trying to run Che on my Mac. I can install Che, create workspaces, and connect to them all fine from my Mac. When I then go to my PC, I can connect to Che, but am unable to connect to my workspaces. I have used this command line to install Che:
docker run --rm -t -v /var/run/docker.sock:/var/run/docker.sock -e CHE_IP=192.168.128.19 -e CHE_HOST_IP=192.168.128.19 -e CHE_DOCKER_MACHINE_HOST_EXTERNAL=192.168.129.19 eclipse/che:5.0.0-latest start
When I look at the network connections in Chrome on my PC, it is showing attempted connections to localhost instead of 192.168.128.19 when I try and open a workspace. Would the change above account for this? Is Che supposed to work on the Mac for remote connections?
Here is what I have installed on my Mac:
@l0rd, I have not. I am very much a newbie and therefore I am trying to follow the directions below and not stray too far from that recommended path:
That says that the docker launcher is the preferred method of running Eclipse Che. As you can see from the above, I've tried to pass in every environment variable that I can to make Eclipse Che on Mac work from remote machines. I even followed the recommendation from CheConf16 yesterday and added an alias to my lo0 (Which I would prefer to remove as it did not seem to help):
Darrins-MacBook-Pro:dhs-cloud dsimmons$ ifconfig
For now, I have gotten Eclipse Che working on a different CentOS box, including remote access to that box, so I can move forward.
Is Eclipse Che supposed to work using the docker launcher with remote access enabled, or is that a use case that is not supported yet? I've tried just about every combination within the context of using the docker launcher to no avail. If it is supposed to work, can I provide any additional info to help sort it out, or should I move this discussion into an issue elsewhere?
I love the work that the team is doing to make Che a dead-simple install and am happy to help in any way I can, if even by just being a "dumb user".
@benoitf, same result. (Great session at CheConf16 yesterday!)
I can access Che, start workspaces, and access workspaces from my Mac. I can access Che and start workspaces from PC, but I cannot access workspaces from my PC. In Chrome on my PC, it shows Che trying to access localhost for the wsagents.
Below is my following the suggestion above along with a docker inspect of che-server. Remember, I still have the lo0 alias to 192.168.65.2. (Don't know if my PC will connect without it or not.) I like the idea of starting Che from a docker instance, so I believe I can just delete the ./che directory on my Mac. Interestingly, When I ran Che directly on my Mac, it found the dockerized Che workspace I had created previously. I've not found where the workspaces are kept on the host machine yet, although I've not looked very hard.
Darrins-MacBook-Pro:dhs-cloud dsimmons$ docker stop che-server
INFO: ECLIPSE CHE: Found image eclipse/che-server:5.0.0-latest
@darrinsimmons - Yeah, given the direction you are taking this issue, it would be helpful to open a new ticket, and document all of the steps that you are following to create the connectivity problem between Mac and Windows. I don't think this pull request is related to this particular problem.