Comments (8)
Hello,
Yes, this file is used by default, but in the image, we have exported CHE_LOCAL_CONF_DIR=/home/user/.che and placed properties file into that directory.
So, you need to mount /home/user/.che/che.properties
from che.
@eivantsov Thanks!
from che.
Hi,
I'm trying to change DOCKER_HOST_IP= 172.17.0.1. It is always getting this value. Is there any to change?
I already tried:
-
Changing /home/user/.che/che.properties
machine.docker.local_node_host=IP1 -
Changing /home/user/che/conf/che.properties
machine.docker.local_node_host=IP1
docker run --rm -t -e CHE_HOST_IP="IP1" -v /var/run/docker.sock:/var/run/docker.sock eclipse/che start
For both attempts above 1 and 2 don't work, number 3 work, but change only:
INFO: ECLIPSE CHE: Use: http://IP1:8080
INFO: ECLIPSE CHE: API: http://IP1:8080/swagger
If I call "che info" I can still see old entries point to 172.17.0.1.
Any clue?
from che.
Why are you trying to change DOCKER_HOST_IP?
from che.
I'm trying to follow https://eclipse-che.readme.io/docs/networking#native-process-for-che-native-docker-for-workspace. Make "docker-ip" and "workspace-ip" have external access and not 172.17.0.1.
from che.
Are we looking at the same docs - I think you maybe have some old links. Are you studying this page?
https://eclipse-che.readme.io/docs/networking
It's not clear why you should set docker-ip to be external, that is an internal system that only Che uses. the only thing you should have to configure is CHE_HOST_IP to make workspaces externally accessible.
from che.
From the same link, I have highlight in bold. It is saying both ip must be reachable by the browser.
"The browser client initiates communication with the Che server by connecting to che-ip. This IP address must be accessible by your browser clients. Internally, Che runs on Tomcat which is bound to port 8080. This port can be altered with Configuration.
When a user creates a workspace, the Che server connects to the Docker daemon at docker-ip and uses the daemon to launch a new set of containers that will power the workspace. These workspace containers will have a Docker-configured IP address, workspace-ip. The workspace-ip must also be reachable by your browser host."
I'm facing same issues related others, I can't start the workspace. The ports are opened. Any idea?
2016-09-16 19:32:25,349[nio-4401-exec-1] [WARN ] [o.e.c.impl.ContainerResponse 93] - Client has aborted connection. Response writing omitted.
2016-09-16 19:32:25,349[nio-4401-exec-2] [WARN ] [o.e.c.impl.ContainerResponse 93] - Client has aborted connection. Response writing omitted.
2016-09-16 19:33:04,899[ted-scheduler-0] [ERROR] [.w.s.WsAgentAnalyticsAddresser 37] - Failed to send agent analytics
java.net.UnknownHostException: install.codenvycorp.com
from che.
We hvae some posting guidelines. Please create a new GitHub issue. You need to provide a step by step set of instructions of what you configured. You need to provide all of your host, OS, docker configuration details.
You should only need to:
- Get docker installed
- Get the Che CLI
- export CHE_HOST_IP=
- che start
If that doesn't work properly, then post all logs and explanation of what you see including output of chrome dev console. Thx!
from che.
Related Issues (20)
- Deploy Che step is failing for the Smoke test of Che-Code HOT 6
- As an admin, I would like to specify the `allowList` of the URLs based on which workspaces / CDEs can be started
- "Restart from local devfile" option resulting in http error HOT 9
- In the Che CR provide a way to set the runtime class for all CDE pods HOT 2
- Move stow / kubedoc and other internal features to the Universal Base Image
- Depreacte and remove ubi 8 from the upstream UDI codebase (ubi 9 should be only supported version in the upstream)
- Prevent users from changing `controller.devfile.io/storage-type` on an existing workspace to avoid confusing & frustrating data loss
- Improve behaviour for Restart From Local Devfile action
- Improve error message of dsc/chectl if OpenShift version cannot be determined
- Devfile 2.3.0 support on the Che-Code side
- Che-Code automatic rebase against upstream VS Code is failed
- Increase DNS timeout for `dsc server:deploy` HOT 2
- Upgrade version of devfile/api to 2.3.0
- Release Eclipse Che 7.89.0
- Che-server devfile V1 cleanup
- Resource monitor doesn't work HOT 2
- Restart from Local Devfile fails if the devfile specifies which container to inject the IDE into HOT 6
- Link to Mattermost is broken in docs HOT 1
- chectl: It seems no check OIDC provider configured using `getEnsureOIDCProviderInstalledTask` Task HOT 3
- Issues with Websockets for Che with Nginx-Ingress Controller. HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from che.