Skip to content

Instantly share code, notes, and snippets.

@kastork
Last active August 30, 2018 18:18
Show Gist options
  • Save kastork/3d060691e9661064e894c2aa1893e0f4 to your computer and use it in GitHub Desktop.
Save kastork/3d060691e9661064e894c2aa1893e0f4 to your computer and use it in GitHub Desktop.
Get Eclipse Che to work on Docker for Mac

Getting Docker for Mac to run Eclipse Che

All of this can be found in the Che docs, but not all in one place.

IP Alias

You must set up the ip alias with a specific IP address (the subnet is not good enough)

yes

› docker run --rm --net host eclipse/che-ip:nightly
192.168.65.3
› sudo ifconfig alias lo0 192.168.65.3

no

Look at value in Docker -> Preferences -> Advanced and find 192.168.65.0/24

› sudo ifconfig alias lo0 192.168.65.0    # or 192.168.65.0/24

NO_PROXY

Despite numerous issues and complaints by many people to the Docker for Mac team, there is no way to set a value for no_proxy on the docker daemon. Therefore you always see this warning:

INFO: Proxy: HTTP_PROXY=gateway.docker.internal:3128, HTTPS_PROXY=gateway.docker.internal:3129, NO_PROXY=
WARN: Potential networking issue discovered!
WARN: We have identified that http and https proxies are set but no_proxy is not. This may cause fatal networking errors. Set no_proxy for your Docker daemon!

But Che has the environment variable CHE_NO_PROXY, which gets set correctly without any action. But you must also set CHE_IN_VM to TRUE (this situation is supposed to be auto-detected to set this automatically, but it isn't.)

So the proper start command ends up being:

docker run -ti -v /var/run/docker.sock:/var/run/docker.sock -v <local data direcrory>:/data -e CHE_IN_VM=true eclipse/che start
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment