Docker system.d service not working (domoticz)

soyxan · May 20, 2019 at 11:38 AM

Hello I am trying to run domoticz on boot as a docker container, so I have the following "domoticz.service" file in /storage/.config/system.d

Code

[Unit]
Description=Domoticz Container
Requires=service.system.docker.service
After=service.system.docker.service

[Service]
Restart=no
RestartSec=10s
TimeoutStartSec=0
ExecStart=/storage/.kodi/addons/service.system.docker/bin/docker start domoticz
ExecStop=/storage/.kodi/addons/service.system.docker/bin/docker stop domoticz

[Install]
WantedBy=multi-user.target

Display More

After a reboot the domoticz container starts (I can see it running from "docker ps" command), but after some seconds it suddenly stops. If I enable the parameter "Restart" to "Allways" the docker container keeps starting and stopping in a loop.

If I check the container logs with the command "docker logs domoticz", I get the following:

Code

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 10-adduser: executing...
usermod: no changes
-------------------------------------
_         ()
| |  ___   _    __
| | / __| | |  /  \
| | \__ \ | | | () |
|_| |___/ |_|  \__/
Brought to you by linuxserver.io
We gratefully accept donations at:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------
User uid:    0
User gid:    0
-------------------------------------
[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-config: executing...
[cont-init.d] 30-config: exited 0.
[cont-init.d] 99-custom-scripts: executing...
[custom-init] no custom scripts found exiting...
[cont-init.d] 99-custom-scripts: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
2019-05-20 12:29:53.084  Status: Domoticz V4.10740 (c)2012-2019 GizMoCuz
2019-05-20 12:29:53.084  Status: Build Hash: 34b73c19, Date: 2019-05-12 18:47:31
2019-05-20 12:29:53.085  Status: Startup Path: /var/lib/domoticz/
2019-05-20 12:29:53.648  Sunrise: 06:54:00 SunSet: 21:29:00
2019-05-20 12:29:53.648  Day length: 14:35:00 Sun at south: 14:11:00
2019-05-20 12:29:53.648  Civil twilight start: 06:22:00 Civil twilight end: 21:60:00
2019-05-20 12:29:53.648  Nautical twilight start: 05:43:00 Nautical twilight end: 22:39:00
2019-05-20 12:29:53.648  Astronomical twilight start: 04:59:00 Astronomical twilight end: 23:23:00

Display More

If I run the ExecStart command manually it works perfectly. What is wrong?

Thanks!

**vpeter** · May 20, 2019 at 1:47 PM

It starts for me fine. What was the command to create domoticz container?

**aptalca** · May 20, 2019 at 2:00 PM

Quote from soyxan

Hello I am trying to run domoticz on boot as a docker container, so I have the following "domoticz.service" file in /storage/.config/system.d

Code

[Unit]
Description=Domoticz Container
Requires=service.system.docker.service
After=service.system.docker.service

[Service]
Restart=no
RestartSec=10s
TimeoutStartSec=0
ExecStart=/storage/.kodi/addons/service.system.docker/bin/docker start domoticz
ExecStop=/storage/.kodi/addons/service.system.docker/bin/docker stop domoticz

[Install]
WantedBy=multi-user.target

Display More

After a reboot the domoticz container starts (I can see it running from "docker ps" command), but after some seconds it suddenly stops. If I enable the parameter "Restart" to "Allways" the docker container keeps starting and stopping in a loop.

If I check the container logs with the command "docker logs domoticz", I get the following:

Code

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 10-adduser: executing...
usermod: no changes
-------------------------------------
_         ()
| |  ___   _    __
| | / __| | |  /  \
| | \__ \ | | | () |
|_| |___/ |_|  \__/
Brought to you by linuxserver.io
We gratefully accept donations at:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------
User uid:    0
User gid:    0
-------------------------------------
[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-config: executing...
[cont-init.d] 30-config: exited 0.
[cont-init.d] 99-custom-scripts: executing...
[custom-init] no custom scripts found exiting...
[cont-init.d] 99-custom-scripts: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
2019-05-20 12:29:53.084  Status: Domoticz V4.10740 (c)2012-2019 GizMoCuz
2019-05-20 12:29:53.084  Status: Build Hash: 34b73c19, Date: 2019-05-12 18:47:31
2019-05-20 12:29:53.085  Status: Startup Path: /var/lib/domoticz/
2019-05-20 12:29:53.648  Sunrise: 06:54:00 SunSet: 21:29:00
2019-05-20 12:29:53.648  Day length: 14:35:00 Sun at south: 14:11:00
2019-05-20 12:29:53.648  Civil twilight start: 06:22:00 Civil twilight end: 21:60:00
2019-05-20 12:29:53.648  Nautical twilight start: 05:43:00 Nautical twilight end: 22:39:00
2019-05-20 12:29:53.648  Astronomical twilight start: 04:59:00 Astronomical twilight end: 23:23:00

Display More

If I run the ExecStart command manually it works perfectly. What is wrong?

Thanks!

Why don't you use the docker addon?

soyxan · May 21, 2019 at 10:45 AM

Quote from vpeter

It starts for me fine. What was the command to create domoticz container?

Code

docker create --name=domoticz -e PUID=0 -e PGID=0 -e TZ=Europe/Madrid -p 7070:8080 -p 6144:6144 -p 7443:1443 -v /storage/domoticz/:/config --device /dev/ttyACM0:/dev/ttyACM0 --restart unless-stopped linuxserver/domoticz

soyxan · May 21, 2019 at 10:49 AM

Quote from aptalca

Why don't you use the docker addon?

I am using docker as an addon, installed from Libreelec repository (service.system.docker).

I have found that there is a domoticz addon from Linuxserver repository, but I feel more confident managing docker from the command line.

**vpeter** · May 21, 2019 at 3:11 PM

When creating docker try without --restart unless-stopped.

soyxan · May 22, 2019 at 9:27 AM

Quote from vpeter

When creating docker try without --restart unless-stopped.

I have created the docker container removing that parameter but nothing changes.

It seems that domoticz is started but then somehow it exits/gets killed.

If I run the command "systemct start domoticz.service" and just after that I run "systemctl status domoticz" I get the following:

Code

● domoticz.service - Domoticz Container
Loaded: loaded (/storage/.config/system.d/domoticz.service; enabled; vendor preset: disabled)
Active: active (running) since Wed 2019-05-22 10:24:01 CEST; 1s ago
Process: 1998 ExecStop=/storage/.kodi/addons/service.system.docker/bin/docker stop domoticz (code=exited, status=0/SUCCESS)
Main PID: 2274 (docker)
Memory: 5.2M
CGroup: /system.slice/domoticz.service
└─2274 /storage/.kodi/addons/service.system.docker/bin/docker start domoticz

May 22 10:24:01 kodi systemd[1]: Started Domoticz Container.

Just after that one I run the same command and I get:

Code

● domoticz.service - Domoticz Container
Loaded: loaded (/storage/.config/system.d/domoticz.service; enabled; vendor preset: disabled)
Active: deactivating (stop) since Wed 2019-05-22 10:25:07 CEST; 755ms ago
Process: 2716 ExecStart=/storage/.kodi/addons/service.system.docker/bin/docker start domoticz (code=exited, status=0/SUCCESS)
Main PID: 2716 (code=exited, status=0/SUCCESS); Control PID: 2889 (docker)
Memory: 4.9M
CGroup: /system.slice/domoticz.service
└─2889 /storage/.kodi/addons/service.system.docker/bin/docker stop domoticz

May 22 10:25:06 kodi systemd[1]: Started Domoticz Container.
May 22 10:25:07 kodi docker[2716]: domoticz

Display More

And if I run the same command again:

Code

● domoticz.service - Domoticz Container
Loaded: loaded (/storage/.config/system.d/domoticz.service; enabled; vendor preset: disabled)
Active: inactive (dead) since Wed 2019-05-22 10:25:09 CEST; 2s ago
Process: 2889 ExecStop=/storage/.kodi/addons/service.system.docker/bin/docker stop domoticz (code=exited, status=0/SUCCESS)
Process: 2716 ExecStart=/storage/.kodi/addons/service.system.docker/bin/docker start domoticz (code=exited, status=0/SUCCESS)
Main PID: 2716 (code=exited, status=0/SUCCESS)

May 22 10:25:06 kodi systemd[1]: Started Domoticz Container.
May 22 10:25:07 kodi docker[2716]: domoticz
May 22 10:25:09 kodi docker[2889]: domoticz

And domoticz container is not running ("docker ps -a"):

Code

CONTAINER ID        IMAGE                  COMMAND             CREATED             STATUS                     PORTS               NAMES
c7cf291ef6b6        linuxserver/domoticz   "/init"             15 minutes ago      Exited (0) 5 minutes ago                       domoticz

What can I do?

Thanks!

**vpeter** · May 22, 2019 at 9:33 AM

After you create domoticz container do you run it from console to initialize it? Because I can run it just fine.

Code

docker start domoticz

# look if completely started with
docker logs domoticz

soyxan · May 22, 2019 at 9:59 AM

Quote from vpeter
After you create domoticz container do you run it from console to initialize it? Because I can run it just fine.
Code
docker start domoticz

# look if completely started with
docker logs domoticz

Yes, after creating the container I run for the first time with "docker start domoticz".

Later, anytime I run from the console with "docker start domoticz" it works perfectly, that is why I do not know why is not working as a service.

**vpeter** · May 22, 2019 at 10:05 AM

Then I can't help you anymore. I only create container and for me it runs fine after reboot too.

soyxan · May 22, 2019 at 11:37 AM

Quote from vpeter

Then I can't help you anymore. I only create container and for me it runs fine after reboot too.

And how did you managed to run after reboot? autostart.sh or systemd.d? Can you share the contents of your system.d service file for domoticz?

**vpeter** · May 22, 2019 at 12:17 PM

Try with this Start and Stop:

Code

ExecStart=/storage/.kodi/addons/service.system.docker/bin/docker start -a domoticz
ExecStop=/storage/.kodi/addons/service.system.docker/bin/docker stop -t 2 domoticz

soyxan · May 22, 2019 at 1:36 PM

Quote from vpeter

Try with this Start and Stop:

Code

ExecStart=/storage/.kodi/addons/service.system.docker/bin/docker start -a domoticz
ExecStop=/storage/.kodi/addons/service.system.docker/bin/docker stop -t 2 domoticz

Yes, now it is wroking! Do you have any explanation for that?

Thanks anyway!

**vpeter** · May 22, 2019 at 1:48 PM

Quote from soyxan

Do you have any explanation for that?

No actually. I just look around how other docker services are started and saw this small change. Maybe

Code

--attach , -a Attach STDOUT/STDERR and forward signals
-t, --time int Seconds to wait for stop before killing it (default 10)