"cannot enable tty mode on non tty input" on Eclipse Che version 4.7.0

[thyeun]

OS : windows 10 build 10240
Docker : boot2docker v1.11.2
Che version : 4.7.0

Cant even start Eclipse Che 4.7.0

[TylerJewell]

set IS_INTERACTIVE=false or IS_TTY=false. See: https://eclipse-che.readme.io/docs/configuration#section-environment-variables

[thyeun]

@TylerJewell after the set result as below

[thyeun]

@TylerJewell inside the che.sh file (newer version), i have to change the line 165 -t to -i, to make it work

docker_run_with_pseudo_tty() {
if has_pseudo_tty; then
docker_run_with_env_file -t "$@"
else
docker_run_with_env_file "$@"
fi
}

[thyeun]

@TylerJewell after go into IDE, i'm getting another error, as below picture.

[TylerJewell]

It doesn't look like you are getting a clean run of the cli. There are errors appearing in the run. Are you in a Windows shell - not a bash shell?

[thyeun]

@TylerJewell this is the result after with Che start

but i still getting the same error from the IDE

[thyeun]

@TylerJewell more info regarding the fail start of workspaces (for current now)

It is only happen for Java stack and blank stack, (python stack are working fine, python stack will pull the latest file from docker)

[TylerJewell]

You are using boot2docker - is there any chance that the VM is out of disk space? Can you SSH into the VM and then do a "df" command to take a look around?

[thyeun]

@TylerJewell result as below

which should delete?

[TylerJewell]

Something is maxing out your disk in that VM. If you are using boot2docker and you have saved your stuff properly, have you thought about destroying the VM and starting again? It would be something like docker-machine rm default, or something similar.

[thyeun]

@TylerJewell i understand now, after remove it, i have create again

[thyeun]

@TylerJewell can you educated me, why it will full? i'm really dont understand, i only use it for my VBox only use for Eclipse Che

[TylerJewell]

Virtualization is a very different sort of world. There could be a lot of reasons that cause this, many of them beyond our understanding. But all VMs are a fixed size - so maybe we hit some mythical limit with all of the docker images loaded into the system.

[thyeun]

@TylerJewell so educational for this, thanks a lot!