-
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
How to use che.sh to run a custom docker image? #608
Comments
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? |
che.sh has something like:
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 |
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. |
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 |
Che shoukd be stabilizing quite quickly these days. So surprised to hear the nightly is behaving badly. Any specific issues? |
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 |
Closing this issue, as it's out of Che script scope. You may hack the script itself as Tyler has suggested. |
The
che.sh
provides some nice configurations for running che, but the-i
related options can only be used with che official images, like:But I have build some che images by myself, which is under
nowind/che
namespace. I can't find a way to pass it toche.sh
shell.Is it possible to make che.sh supports custom images?
The text was updated successfully, but these errors were encountered: