-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Stop of Che container in new Che launcher is broken #1949
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
garagatyi
added
the
kind/bug
Outline of a bug - must adhere to the bug report template.
label
Jul 26, 2016
riuvshin
added
the
severity/blocker
Causes system to crash and be non-recoverable or prevents Che developers from working on Che code.
label
Jul 26, 2016
@TylerJewell this is exactly the problem I experienced. Once there is a PR I will be willing to test it out. |
@jcpowermac - in diagnostics, it seems to be error in the way that che-launcher executes a stop. I experienced it yesterday on MacOS. |
For @l0rd to fix. |
l0rd
added a commit
to l0rd/che
that referenced
this issue
Jul 26, 2016
Signed-off-by: Mario Loriedo <[email protected]>
TylerJewell
pushed a commit
that referenced
this issue
Jul 26, 2016
Signed-off-by: Mario Loriedo <[email protected]>
tolusha
pushed a commit
that referenced
this issue
Aug 1, 2016
Signed-off-by: Mario Loriedo <[email protected]>
ShimonBenYair
pushed a commit
to ShimonBenYair/che
that referenced
this issue
Aug 4, 2016
…#1956) Signed-off-by: Mario Loriedo <[email protected]>
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.
New Che launcher stop Che and suppresses error output. Then container is removed with docker rm -f.
Because of that Che doesn't store created workspaces and other information into data storage folder.
Reproduction Steps:
Expected behavior:
Created workspace exists
Observed behavior:
There is no workspaces in Che
Che version: 4.6.0-Snapshot
OS and version: Ubuntu 14.04
Docker version: 1.11.2
Che install: Docker container
Additional information:
The text was updated successfully, but these errors were encountered: