EdgarWallace

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='openHAB' --net='br0' --ip='192.168.178.22' --cpuset-cpus='5' --privileged=true -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -v '/etc/localtime':'/etc/localtime':'ro' -v '/mnt/user/system/appdata/openhab/conf/':'/openhab/conf':'rw' -v '/mnt/user/system/appdata/openhab/userdata/':'/openhab/userdata':'rw' --device=/dev/ttyACM0 --shm-size 2g 'openhab/openhab:latest-debian' /bin/chmod o+rw /dev/ttyACM0 && /entrypoint.sh 55c064827917c2b56ce5dbc5983f7d635623dec20f4aca7477e2b0fad4ef2e7c sh: /entrypoint.sh: No such file or directory ...doesn't like the command...

What does that mean please? Should I enter this into the Post Arguments box? /bin/chmod o+rw /dev/ttyACM0 && /entrypoint.sh

If you are using openhab/openhab:latest-debian as openHAB Repository you are getting that update automatically.

Unfortunately openHAB doesn‘t start when I am adding /bin/chmod o+rw /dev/ttyACM0 into the Post Arguments box....

There is on comment on Troubleshooting of OH3: docker exec \ -d \ openhab \ /bin/chmod o+rw /dev/ttyACM0 Is there any way to and that into the Docker template, or how to add ist myself? Maybe adding ist into the Post Arguments?

I was trying to get Collabora running as seperate Docker: I installed the container with default name (collabora), renamed the sample proxy conf, added the subdomain in SWAG and as CNAME at my DNS provider. SWAG log is showing: [cont-init.d] done. [services.d] starting services nginx: [emerg] "server" directive is not allowed here in /config/nginx/proxy-confs/collabora.subdomain.conf:3 Server ready nginx: [emerg] "server" directive is not allowed here in /config/nginx/proxy-confs/collabora.subdomain.conf:3 nginx: [emerg] "server" directive is not allowed here in /config/nginx/proxy-confs/collabora.subdomain.conf:3 nginx: [emerg] "server" directive is not allowed here in /config/nginx/proxy-confs/collabora.subdomain.conf:3 nginx: [emerg] "server" directive is not allowed here in /config/nginx/proxy-confs/collabora.subdomain.conf:3 ...... [cont-init.d] done. [services.d] starting services nginx: [emerg] "server" directive is not allowed here in /config/nginx/proxy-confs/collabora.subdomain.conf:3 Server ready nginx: [emerg] "server" directive is not allowed here in /config/nginx/proxy-confs/collabora.subdomain.conf:3 nginx: [emerg] "server" directive is not allowed here in /config/nginx/proxy-confs/collabora.subdomain.conf:3 nginx: [emerg] "server" directive is not allowed here in /config/nginx/proxy-confs/collabora.subdomain.conf:3 nginx: [emerg] "server" directive is not allowed here in /config/nginx/proxy-confs/collabora.subdomain.conf:3 ...... I thought that I followed @SpaceInvaderOne guide quite well but obviously I made a mistake.....

Thanks @saarg because I would need to set up a subdomain which is much more complex than using the build in Collabora (or Onlyoffice) app. I might be better off migrating to knex666 Nextcloud docker with full Onlyoffice integration based on Apache.

Thanks @BRiT that is working great!!!

Sorry to bother again....is it realistic waiting for a fix of the integrated Collabora App? Thanks a lot.

Thanks a lot @saarg I just need one of these apps Collabora would be perfectly fine. I got the link from Collabora. AppImages does not run on Alpine which is the root cause that integrated Collabora app isn‘t running on Alpine Dockers....at least how I understood it.

I would kindly ask for advise: I was never successful in having the Collabora or Onlyoffice Docker running with my Nextcloud install and having read @saarg post is not giving big hope. The Collabora support replied on my question that I am getting an error message by accessing the build-in Collabora app: linuxserver.io Nextcloud docker is based on Alpine which uses musl libc instead of glibc - and AppImages do not work with musl libc: https://github.com/AppImage/AppImageKit/issues/1015 I would like to stick to my linuxserver.io Nextcloud install that is running rock solid since years rather than using another Nextcloud container. Is there a small chance that the issues will be resolved from your linuxserver.io side? Really, that is a question, NOT a complaint. Thank you.

A question to that command if I want to just "immutable" certain files. I was trying e.g.: find /mnt/disk2/Kino/*.m4v -type f -exec chattr +i "{}" \; That is working well except with sub-directories. I was trying to use the -R (recursively changes attributes of directories and their contents) flag but this is not working. HAs anyone tried this? Thanks a lot.

Thanks a lot @ich777 Yes I indeed forwarded TCP and UDP and made the test. Results are attached, I do believe that this is looking fine? However, it takes ages, until someone is accepted to enter a TALK meeting. Did you made the same experience?

Hi, great work on the STUN-TURN-Server. Just asking for confirmation if I understood correct that I haver to open port 5349 in my router? And then adding myownnetwork.com:5349 into the STUN & TURN settings of Nextcloud/Settings/Talk? Thanks a lot.

@Menthalo I don't see that variable in my Docker settings. HAve you defined it yourself?