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

changing recipe location causes an error #3447

Closed
aleksei-burlakov opened this issue Dec 20, 2016 · 2 comments
Closed

changing recipe location causes an error #3447

aleksei-burlakov opened this issue Dec 20, 2016 · 2 comments
Labels
kind/question Questions that haven't been identified as being feature requests or bugs.

Comments

@aleksei-burlakov
Copy link

Changing recipe location to something else rather than codenvy/ubuntu_jdk8 causes an error when startin the workspace.

Reproduction Steps:

I have created a workspace 'default blank'. It's default recipe location is codenvy/ubuntu_jdk8

"recipe": {
        "location": "codenvy/ubuntu_jdk8",
        "type": "dockerimage"
      }

I have also created a new docker image using $docker commit command and pushed to the docker hub. The new image is based on codenvy/ubuntu_jdk8 and it's name is marmolata/ubuntu_jdk8_123

When I change the receipe location to

"recipe": {
        "location": "marmolata/ubuntu_jdk8_123",
        "type": "dockerimage"
      }

then I have an error when start the workspace. I also tried with other images, like

"recipe": {
        "location": "ubuntu",
        "type": "dockerimage"
      }

or

"recipe": {
        "location": "ankitkariryaa/sbt-javac",
        "type": "dockerimage"
      }

and it only failed to start.

Expected behavior:

I expect it would work as if it was codenvy/ubuntu_jdk8.

Observed behavior:

screenshot from 2016-12-20 14-07-05

Che version: 5.0.0-latest
OS and version: Ubuntu 16.04 LTS
Docker version: 1.12.1, build 23cf638

Additional information:

  • Problem started happening recently, didn't happen in an older version of Che: Yes
  • Problem can be reliably reproduced, doesn't happen randomly: Yes
@ghost ghost added the kind/question Questions that haven't been identified as being feature requests or bugs. label Dec 21, 2016
@ghost
Copy link

ghost commented Dec 21, 2016

@aleksei-burakov you need a non terminating CMD in your recipe. Can you add tailf /dev/null to your CMD, rebuild and re-upload an image?

@aleksei-burlakov
Copy link
Author

Thank you! That worked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/question Questions that haven't been identified as being feature requests or bugs.
Projects
None yet
Development

No branches or pull requests

1 participant