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

CHE_HOST variable is not working as expected #3350

Closed
skabashnyuk opened this issue Dec 12, 2016 · 5 comments
Closed

CHE_HOST variable is not working as expected #3350

skabashnyuk opened this issue Dec 12, 2016 · 5 comments
Assignees
Labels
kind/bug Outline of a bug - must adhere to the bug report template. severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code.
Milestone

Comments

@skabashnyuk
Copy link
Contributor

I want to pass CHE_HOST=172.19.20.18 to che cli to be able to use che from remote host.
Che started successfully. Workspace started but not able to communicate with master.
In che.env variable CHE_HOST was commented.
Reproduction Steps:

  1. start che docker run -it --rm -e "CHE_HOST=172.19.20.18" -v /var/run/docker.sock:/var/run/docker.sock -v $HOME/.che/data:/data -v $HOME/dev/src/codenvy/che:/repo eclipse/che-cli:nightly start
  2. Start workspace

Expected behavior:
workspace started
Observed behavior:
workspace is not able to start

Additional information:

sj@sj-i7:~]$ docker version
Client:
Version: 1.12.3
API version: 1.24
Go version: go1.6.3
Git commit: 6b644ec
Built: Wed Oct 26 22:01:48 2016
OS/Arch: linux/amd64

Server:
Version: 1.12.3
API version: 1.24
Go version: go1.6.3
Git commit: 6b644ec
Built: Wed Oct 26 22:01:48 2016
OS/Arch: linux/amd64

@skabashnyuk skabashnyuk added the kind/bug Outline of a bug - must adhere to the bug report template. label Dec 12, 2016
@skabashnyuk
Copy link
Contributor Author

After I've edit che.env and set CHE_HOST=172.19.20.18 workspace started successfully

@skabashnyuk skabashnyuk added this to the 5.0.0-M9 milestone Dec 12, 2016
@vparfonov vparfonov added the severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code. label Dec 12, 2016
@TylerJewell
Copy link

Just to confirm - the Che host is not being written into Che.env when you first do an installation?

@skabashnyuk
Copy link
Contributor Author

NO. CHE_HOST was commented out.

@TylerJewell TylerJewell self-assigned this Dec 12, 2016
@TylerJewell
Copy link

Bug confirmed. It seems that in the refactoring, the ability to assignt this variable was altered.

@TylerJewell
Copy link

Fixed in #3345.

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. severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code.
Projects
None yet
Development

No branches or pull requests

4 participants