OH3 portainer ./start.sh failed: No such file or directory

Upgrading hardware from RPi (running fine) to NUC where installed Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-50-generic x86_64) + OpenJDK Runtime Environment (build 11.0.11+9-Ubuntu-0ubuntu2.20.04) with Docker 20.10.2 and Portainer 1.24.2.

Managed to get all working even openhab container is “running” but http://localhost:8080 returns via Firefox on Ubuntu machine “unable to connect”.

See full log further below where it ends with:

++ 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
**[FATAL tini (24)] exec ./start.sh failed: No such file or directory**

Please find attached pictures of the portainer configuration where I have followed the instructions from the OH3 documentation.
Also I have seen a similar post at “not-able-to-start-a-new-installation-of-opernhab-on-synology-dsm-6-2-with-docker-and-portainer” but I could not derive a solution from here.


portainer-2


portainer-5

portainer-7

Can anyone assist? Feels I am almost there :wink:

Full log:

+ echo 'Configuring Zulu JDK 11 unlimited strength cryptography policy...'
Configuring Zulu JDK 11 unlimited strength cryptography policy...
+ '[' 11 = 8 ']'
+ '[' 11 = 11 ']'
+ java_security_file=/usr/lib/jvm/default-jvm/conf/security/java.security
+ sed -i 's/^crypto.policy=limited/crypto.policy=unlimited/' /usr/lib/jvm/default-jvm/conf/security/java.security
+ rm -f /openhab/runtime/instances/instance.properties
+ rm -f /openhab/userdata/tmp/instances/instance.properties
+ NEW_USER_ID=998
+ NEW_GROUP_ID=998
+ echo 'Starting with openhab user id: 998 and group id: 998'
Starting with openhab user id: 998 and group id: 998
+ id -u openhab
+ initialize_volume /openhab/conf /openhab/dist/conf
+ volume=/openhab/conf
+ source=/openhab/dist/conf
++ ls -A /openhab/conf
+ '[' -z 'html
icons
items
persistence
rules
scripts
services
sitemaps
sounds
things
transform' ']'
+ initialize_volume /openhab/userdata /openhab/dist/userdata
+ volume=/openhab/userdata
+ source=/openhab/dist/userdata
++ ls -A /openhab/userdata
+ '[' -z 'etc
logs
tmp' ']'
++ cmp /openhab/userdata/etc/version.properties /openhab/dist/userdata/etc/version.properties
+ '[' '!' -z ']'
+ chown -R openhab:openhab /openhab
+ sync
+ '[' -d /etc/cont-init.d ']'
+ sync
+ '[' false == false ']'
++ 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
[FATAL tini (24)] exec ./start.sh failed: No such file or directory

What I see is you are assuming start.sh is in whatever directory Portainer chooses. The error indicates it is some place else.

Looking at the thread it appears to be related to using the Portainer settings defined by somebody in the community instead of using the developer supported docker software.

This is with “find”:

I have tested using Docker. I prefer using docker run myself but docker-compose should work too. They are both somewhat documented on the Docker Hub page.

https://hub.docker.com/r/openhab/openhab/

Here are the website docs.

On my pure OpenHAB-Container using Portainer, the Working-Dir is /openhab and not /opt/openhab

Maybe that is something you can check.

Kindest regards,
Christian…

1 Like

Yaml worked! THANKS!


Now I have to find the differences in Portainer …

That could very well be the issue for them

I will try later with another one. First difference I see is the volumes and the “ID” is different.

Next challenge is to get the backup from RPi in here. I am gonna miss the config tool :joy:

You were right. Changing the Working Dir as suggested worked. No more errors.

1 Like