I’m attempting to create a new instance of OpenHab on a new server but when I attempt to start the container with empty addons, config, and userdata folders it fails with a “/entrypoint: line 100: exec: not found” error message.
I’ve had OH3 running on a different Synology box for at least a month using the same configuration. I’m using a Docker Create script file to create the containers and have verified that they are the same. The log files seem similar (accounting for the folders under conf & userdata do not exist in the new installation) except for near the end of the log.
Tail of log from working installation:
++ IFS=' '
++ echo gosu openhab tini -s ./start.sh
+ '[' 'gosu openhab tini -s ./start.sh' == 'gosu openhab tini -s ./start.sh' ']'
+ command=($@ server)
+ exec gosu openhab tini -s ./start.sh server
Launching the openHAB runtime...
Tail of log from new (failing) installation:
++ IFS=' '
++ echo $'\r'
+ '[' $'\r' == 'gosu openhab tini -s ./start.sh' ']'
+ exec $'\r'
/entrypoint: line 100: exec: not found
I have verified the folders are in place, the user & group have the same privileges, etc.
Any ideas how to fix this or what else to look at? I’m stumped.
I know very little about Linux and Docker, but my guess is that the “\r” is a variable name that is not being populated. It seems to appear several times in the log where things go haywire (beginning with the echo in the above snips).
After some searching I found the “docker container ls” command the entry point on the working container is
"/entrypoint gosu openhab tini -s ./start.sh"
bur for the non-working container the entry point is
"/entrypoint \r"
I tried adding an --entrypoint parameter to the Docker Create but the “\r” seems to be persistant.
"/entrypoint gosu openhab tini -s ./start.sh \r"
I’ve tried every different permutation of the --entrypoint parameter that I could think of but I haven’t found anything that worked.
