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

How to use che.sh to run a custom docker image? #608

Closed
freewind opened this issue Mar 2, 2016 · 7 comments
Closed

How to use che.sh to run a custom docker image? #608

freewind opened this issue Mar 2, 2016 · 7 comments
Labels
kind/question Questions that haven't been identified as being feature requests or bugs.

Comments

@freewind
Copy link

freewind commented Mar 2, 2016

The che.sh provides some nice configurations for running che, but the -i related options can only be used with che official images, like:

che.sh -i run
che.sh -i:nightly run

But I have build some che images by myself, which is under nowind/che namespace. I can't find a way to pass it to che.sh shell.

Is it possible to make che.sh supports custom images?

@TylerJewell
Copy link

That seems like something that would be outside the scope of the Che scripts.

Any thing is possible but what would be the motivation for doing so? If you want to launch custom images you could just launch your own docker run commands. Wouldn't that be easier?

@freewind
Copy link
Author

freewind commented Mar 2, 2016

che.sh has something like:

-p:port
-r:ip
-b
-g

which I think is useful, so I'm thinking to use che.sh to run my own che image. I'm not sure if all the options are useful for images.

PS: my own che image is just a backup of codenvy/che:nightly some days ago, because the "nightly" of these days are not working well. I treat it as an official image without my custom namespace

@TylerJewell
Copy link

You could make a quick modification. The image name I believe is only used in a single location in the entire script. Look up the run command in the script and replace it with a bash variable. The input parameters are easy to extend as well.

@freewind
Copy link
Author

freewind commented Mar 2, 2016

Yes, thanks, I found the location and can modify it easily.

I just think it might be a general requirement, and could be considered go into the official shell

@TylerJewell
Copy link

Che shoukd be stabilizing quite quickly these days. So surprised to hear the nightly is behaving badly. Any specific issues?

@freewind
Copy link
Author

freewind commented Mar 2, 2016

Post it here: #609

This issue has been appeared since after 2016-02-16. I just tried latest nightly build, still has the same problem

@ddementieva ddementieva added the kind/question Questions that haven't been identified as being feature requests or bugs. label Mar 2, 2016
@ghost
Copy link

ghost commented Mar 2, 2016

Closing this issue, as it's out of Che script scope.

You may hack the script itself as Tyler has suggested.

@ghost ghost closed this as completed Mar 2, 2016
This issue was closed.
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

3 participants