Domoticz in Docker not running on buster

[Kedi]

So I am still on Buster. I could install Domoticz on docker and use customstart.sh
The first command in that file -> apt-get update gives me this output:

Code: Select all

    
1970-01-01 01:00:00.000  Launch: Begin container self-repair
1970-01-01 01:00:00.000  Launch: End container self-repair
1970-01-01 01:00:00.000  Launch: Running customstart.sh

updating packages

Get:1 http://deb.debian.org/debian bookworm InRelease [151 kB]
Get:2 http://deb.debian.org/debian bookworm-updates InRelease [55.4 kB]
Get:3 http://deb.debian.org/debian-security bookworm-security InRelease [48.0 kB]

It never proceeds after the last Get:3 so Domoticz never starts
Anybody with the same issue and has a solution?

[waltervl]

To test, what happens if you do not use customstart.sh.
It should start. Then login to the container and run apt-get update ? Will the update also not continue?

[Kedi]

It even got worse. The container will not start with this error.

Code: Select all

Current thread 0xb6f8c010 (most recent call first):
<no Python frame>
terminate called without an active exception
1931-01-01 11:31:05.000  Error: Domoticz(pid:1, tid:1('domoticz')) received fatal signal 6 (Aborted)
1931-01-01 11:31:05.000  Error: siginfo address=0x1, address=0xb6a21a21
sh: 1: pkill: not found
1931-01-01 11:31:05.000  Error: Failed to start gdb, will use backtrace() for printing stack frame
1931-01-01 11:31:05.000  Error: #0  /opt/domoticz/domoticz :  + 0x279ddc [0x729ddc]
1931-01-01 11:31:05.000  Error: #1  /opt/domoticz/domoticz : signal_handler(int, siginfo_t*, void*) + 0x1bd [0x72a5a2]
1931-01-01 11:31:05.000  Error: #2  /lib/arm-linux-gnueabihf/libc.so.6 :  + 0x27840 [0xb6a22840]
1931-01-01 11:31:05.000  Error: #3  /lib/arm-linux-gnueabihf/libc.so.6 :  + 0x177e6 [0xb6a127e6]
1931-01-01 11:31:05.000  Error: #4  /lib/arm-linux-gnueabihf/libc.so.6 : gsignal + 0x7b [0xb6a21a20]
1931-01-01 11:31:05.000  Error: Domoticz(pid:1, tid:1('domoticz')) received fatal signal 4 (Illegal instruction) while backtracing
1931-01-01 11:31:05.000  Error: siginfo address=0xb6a123a8, address=0xb6a21a21
1931-01-01 11:31:05.000  Error: #0  /opt/domoticz/domoticz :  + 0x279ddc [0x729ddc]
1931-01-01 11:31:05.000  Error: #1  /opt/domoticz/domoticz : signal_handler(int, siginfo_t*, void*) + 0x1a9 [0x72a58e]
1931-01-01 11:31:05.000  Error: #2  /lib/arm-linux-gnueabihf/libc.so.6 :  + 0x27840 [0xb6a22840]
1931-01-01 11:31:05.000  Error: Domoticz(pid:1, tid:1('domoticz')) received fatal signal 4 (Illegal instruction)
1931-01-01 11:31:05.000  Error: siginfo address=0xb6a123a8, address=0xb6a21a21
sh: 1: pkill: not found
1931-01-01 11:31:05.000  Error: Failed to start gdb, will use backtrace() for printing stack frame
1931-01-01 11:31:05.000  Error: #0  /opt/domoticz/domoticz :  + 0x279ddc [0x729ddc]
1931-01-01 11:31:05.000  Error: #1  /opt/domoticz/domoticz : signal_handler(int, siginfo_t*, void*) + 0x1bd [0x72a5a2]
1931-01-01 11:31:05.000  Error: #2  /lib/arm-linux-gnueabihf/libc.so.6 :  + 0x27840 [0xb6a22840]
1970-01-01 01:00:00.000  Launch: Begin container self-repair
1970-01-01 01:00:00.000  Launch: End container self-repair
touch: setting times of '/opt/domoticz/FIRSTRUN': Operation not permitted
1931-01-01 04:41:29.000  Status: Domoticz V2025.1 (build 16672) (c)2012-2025 GizMoCuz
1931-01-01 04:41:29.000  Status: Build Hash: 7f861f5bd, Date: 2025-05-05 08:31:45
1931-01-01 04:41:29.000  Status: Startup Path: /opt/domoticz/
1931-01-01 04:41:29.000  Error: Default admin password has NOT been changed! Change it asap!
Fatal Python error: init_interp_main: can't initialize time
Python runtime state: core initialized
PermissionError: [Errno 1] Operation not permitted

B.T.W. I rebooted my rasp 4 just to be sure that nothing else is wrong. My default production Domoticz runs fine on that same rasp 4

[waltervl]

You have run the following command while installing docker (using the docker wiki)?

Code: Select all

sudo usermod -aG docker ${USER}

Edit: and also post your docker-compose.yml file.

Edit2: moved this to a separate topic.

[Kedi]

Yes I have run that command. A time ago Domoticz ran in a container on my main system.
I have several rasp pi running also with docker and Domoticz.
The above was the output of domotic:stable
with domoticz:beta Domoticz starts, but when I access the UI via a browser I get these errors;

Code: Select all

1929-02-27 06:36:12.000  Status: ::ffff:192.168.2.47 -> handle abandoned timeout (status=5)
1929-02-27 06:36:12.000  Status: ::ffff:192.168.2.47 -> handle abandoned timeout (status=3)
1929-02-27 06:36:12.000  Status: ::ffff:192.168.2.47 -> handle abandoned timeout (status=5)
1929-02-27 06:36:12.000  Status: ::ffff:192.168.2.47 -> handle abandoned timeout (status=5)
1929-02-27 06:36:12.000  Status: ::ffff:192.168.2.47 -> handle abandoned timeout (status=5)

My compose in Portainer is:

Code: Select all

services:
  domoticz:
    image: domoticz/domoticz:beta
    container_name: domoticz
    restart: unless-stopped
    ports:
      - "9090:8080"
    volumes:
      - /var/lib/docker/volumes/domoticz:/opt/domoticz/userdata
    environment:
      - TZ=Europe/Amsterdam
      - LOG_PATH=/opt/domoticz/userdata/domoticz.log

[Kedi]

I have an other raspberry pi (bookworm) on which I run a docker container for my scale, which works fine.
I installed Domoticz on that raspberry with my compose file and it runs fine.
I am out of options.
So I have to install Domoticz from scratch on an other raspberry with bookworm.
That will take some time, so I better invest that time on installing HomeAssistant and work with that in the future.
Because I don't like supprise on such short notice like this openssl thing.
B.t.w. I tried to install openssl 3.5.0 (LTS) the install went fine, but Domoticz still won't run