You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This may not be a bug. This looks like possibly a caching issue. The --e environment variable was removed from the che.sh script in a recent version. It should only be using --env now when making calls to the codenvy/che-launcher. And the launcher itself didn't seem to make it far enough to call the codenvy/che-server.
Can you wipe your che.sh and grab the latest from master for another test. Also, try ./che info.
Ok - we diagnosed this to a bug with bash "echo" command. For some reason if --env-file is in a bash string, then echo interprets -e as a flag and ignores the n. The solution is to hard code --env-file into the docker run syntax.
Cannot run Che using the CLI on Linux.
Reproduction Steps:
Expected behavior:
Che starts
Observed behavior:
The error occurs when CHE_LOCAL_CONF_DIR is exported in the system. Unsetting it fixes the problem.
The text was updated successfully, but these errors were encountered: