How do I deploy Eclipse Che with a custom version of the Che image?

Summary

Hey all, I’m trying to set up Eclipse Che on OpenShift in an enterprise environment which requires me to make some changes with the Che pod prior to deployment. I made a custom Che image (That is, I built an image using the GitHub project’s filed with a slightly altered Che Dockerfile). I also turned it into a .tar file, so now I have it both deployed on my local computer’s Docker as well as in file form.

I know that when deploying a Che project using deploy_che.sh, I should append the --che-image=<myImage>:<myTag> command to it. This part is not problematic.

However, for security reasons I don’t want to put my custom version of Che on a repository online. How can I move/copy it to OpenShift’s Docker registry so when the project finally deploys, it’ll look for the custom Che image locally and find it instead of looking for it online (Where it doesn’t exist)?

Relevant information

As previously stated, this is Eclipse Che for OpenShift. The custom Che image is very similar to the default Che image, I just added some certificates to its truststore, which is precisely why I don’t want to put it online in a repository, as that would be unsafe. Also, I have the custom image both running on my local Docker and also as a .tar file, so a solution with either will do just fine.

Thanks in advance 😃

[AmitChameides]

Alright. Thank you all for your help. In the end, I wasn’t able to properly set up a private repo which a bot was able to pull from and have OpenShift use that bot. I ended up putting my image on the public DockerHub registry simply because on second thought my image didn’t contain any information that was secret.

I’m closing the issue because my particular issue has been fixed - putting my custom Che image on a public registry and then calling it when generating the project using the image-che= field worked as intended and made my Che project use my custom image. Still, if I did have truly secret information I wasn’t able to put publicly, I’m not sure I would’ve been able to properly set it up in the methods you have described to get everything to work. I’m not very accustomed to all these technologies and still have much to learn.

[amisevsk]

@AmitChameides With a private quay repo (or private docker repo) you could set up a bot account that has pull permissions and then try to set up OpenShift to pull via that bot.

I think this is the canonical solution to deploying a non-public build of Che, but I haven’t done it myself yet.