I would guess that whatever is trying to start the dremio executable is doing so from the wrong directory. If you’re able to change the script that is calling dremio from a relative path (‘bin/dremio’) to a fully qualified path (e.g.: ‘/opt/dremio/bin/dremio’… substitute for the correct path!) that might solve things
Aha, I see. Could you provide your BuildConfig for Dremio on OpenShift?
I think, looking at things, that the Docker working directory must be changed somehow. The command to start Dremio is defined relative to the working directory, and I’m suspecting that the OpenShift build process is changing this somehow.
Currently am working with a customer that successfully has Dremio deployed via Docker in Openshift. To answer your original post, the cmd we used to start Dremio (and what Christy mentioned in using the path) is
sh /opt/dremio/bin/dremio start
that should replace your line 5 in run.sh. Maybe try that?
FYI - your Docker script is pulling a super old Dremio version 1.3.1. We are currently on 2.0.5, probably worth changing
Apologises, I think there was some confusion. The https://hub.docker.com/r/dremio/dremio-oss/ is the official version, and it running an up-to-date Docker. However, this is not the same as the github project lmangani/dremio-docker (this is an earlier unofficial docker image).
The official image is build by us as Dremio.
Hopefully, that’s cleared up. Regarding Anthony’s suggestion in modifying run.sh, are you able to give this a try, or do you need a bit more clarity?