September 10, 20169 yr Added the fhem docker via the CA page. It isn't a proper unraid template, so I'm just trying it. It starts, but there are no files in the config directories. Here is the log. I wondered if it is likely to be something simple? Creating SSH2 RSA key; this may take some time ... 2048 0a:cf:56:e5:9f:29:d8:fd:f1:ee:7e:f2:04:f3:5c:ce /etc/ssh/ssh_host_rsa_key.pub (RSA) Creating SSH2 DSA key; this may take some time ... [key] /etc/ssh/ssh_host_dsa_key.pub (DSA) Creating SSH2 ECDSA key; this may take some time ... [key] /etc/ssh/ssh_host_ecdsa_key.pub (ECDSA) Creating SSH2 ED25519 key; this may take some time ... [key] /etc/ssh/ssh_host_ed25519_key.pub (ED25519) invoke-rc.d: policy-rc.d denied execution of restart. Starting OpenBSD Secure Shell server: sshd. Current directory : /root Environment RUNVAR: fhem There are 0 arguments: No argument supplied. Start supervisord Stopping system message bus: dbus. Starting system message bus: dbus. Stopping rpcbind daemon.... Starting rpcbind daemon.... Stopping automount.... Starting automount...failed (failed to load autofs4 module). Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon. Restarting periodic command scheduler: cronStopping periodic command scheduler: cron. Starting periodic command scheduler: cron. /usr/lib/python2.7/dist-packages/supervisor/options.py:296: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security. 'Supervisord is running as root and it is searching ' 2016-09-10 19:32:51,919 CRIT Supervisor running as root (no user in config file) 2016-09-10 19:32:51,919 WARN Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing 2016-09-10 19:32:51,930 INFO RPC interface 'supervisor' initialized 2016-09-10 19:32:51,930 CRIT Server 'unix_http_server' running without any HTTP authentication checking 2016-09-10 19:32:51,930 INFO supervisord started with pid 182 2016-09-10 19:32:52,932 INFO spawned: 'fhem' with pid 185 2016-09-10 19:32:53,934 INFO success: fhem entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2016-09-10 19:32:54,411 INFO exited: fhem (exit status 2; expected) invoke-rc.d: policy-rc.d denied execution of restart. Starting OpenBSD Secure Shell server: sshd. Current directory : /root Environment RUNVAR: fhem There are 0 arguments: No argument supplied. Start supervisord Stopping system message bus: dbus. Starting system message bus: dbus. mkdir: cannot create directory '/run/sendsigs.omit.d': File exists Stopping rpcbind daemon.... Starting rpcbind daemon.... Stopping automount.... Starting automount...failed (failed to load autofs4 module).
September 10, 20169 yr Community Expert Since you haven't even told us what docker you're using, I suggest you start with this: I need some help! What info does the community need to help me?
September 10, 20169 yr Author Hi Trurl, the docker is fhem_jessie. It is the only fhem docker that shows up in Community Apps. It is here https://hub.docker.com/r/pipp37/fhem_jessie/ Here is the run command. root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="fhem_jessie" --net="bridge" -e TZ="Europe/London" -e HOST_OS="unRAID" -p 2222:2222/tcp -p 7072:7072/tcp -p 8093:8083/tcp -p 8094:8084/tcp -p 8095:8085/tcp -v "/mnt/user/appdata/docker/dockerdata/fhem/opt/fhem/":"/opt/fhem":rw -v "/mnt/user/appdata/docker/dockerdata/fhem/opt/yowsup-config/":"/opt/yowsup-config":rw pipp37/fhem_jessie c283ac7ccadbd45892ad5fe7127bd526b99d6c3a6755401c0e75c313916e3054 The command finished successfully!
September 10, 20169 yr Hi Trurl, the docker is fhem_jessie. It is the only fhem docker that shows up in Community Apps. It is here https://hub.docker.com/r/pipp37/fhem_jessie/ Here is the run command. root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="fhem_jessie" --net="bridge" -e TZ="Europe/London" -e HOST_OS="unRAID" -p 2222:2222/tcp -p 7072:7072/tcp -p 8093:8083/tcp -p 8094:8084/tcp -p 8095:8085/tcp -v "/mnt/user/appdata/docker/dockerdata/fhem/opt/fhem/":"/opt/fhem":rw -v "/mnt/user/appdata/docker/dockerdata/fhem/opt/yowsup-config/":"/opt/yowsup-config":rw pipp37/fhem_jessie c283ac7ccadbd45892ad5fe7127bd526b99d6c3a6755401c0e75c313916e3054 The command finished successfully! You're making the assumption that the container actually works. It may be broken, if i were you the first place I'd seek advice would be from the container author, in my experience there's a lot of broken containers on dockerhub.
Archived
This topic is now archived and is closed to further replies.