searching for a beta domoticz container

[pvklink]

Hi, I am playing with docker icm with IOTSTACK and have an old conatiner with an old domoticz version.
I like to use my current database that belongs to version 2020.2 build 13091 so i need the same docker, is that posible?

I use docker-compose within iotstack so i can define the "right"container...

[pvklink]

I am a little step further.
I find out that you can add tags to specify the domoticz container, like: linuxserver/domoticz:arm32v7-2020.2-ls47

My trial was: linuxserver/domoticz:stable, so that explains why i got an error when using this old container in combination with my latest database which is used by my current non-container production environment, v2020.2 build 13091.

What can i do to use my latest database, version 2020.2 build 13091 in combination with docker, which tag do i specify or do i have to update to another beta domoticz version on my current non container system first?

Code: Select all

Status: Domoticz V2020.2 (c)2012-2020 GizMoCuz
domoticz        | 2021-03-30 07:23:50.180  Status: Build Hash: b63341bc0, Date: 2020-04-26 11:47:55
domoticz        | 2021-03-30 07:23:50.180  Status: Startup Path: /usr/share/domoticz/
domoticz        | 2021-03-30 07:23:50.186  Error: Database incompatible with this Domoticz version. (You cannot downgrade to an old Domoticz version!)
domoticz        | terminate called without an active exception
domoticz        | 2021-03-30 07:23:50.187  Error: Domoticz(pid:346, tid:346('domoticz')) received fatal signal 6 (Aborted)
domoticz        | 2021-03-30 07:23:50.187  Error: siginfo address=0x15a, address=0xb6ae7bcf
domoticz        | 2021-03-30 07:23:50.201  Error: Failed to start gdb, will use backtrace() for printing stack frame
domoticz        |
domoticz        | 2021-03-30 07:23:50.203  Error: #0  /usr/bin/domoticz() [0x2db544]
domoticz        | 2021-03-30 07:23:50.203  Error: #1  /usr/bin/domoticz : signal_handler(int, siginfo_t*, void*) + 0x1f8 [0x2dbf00]
domoticz        | 2021-03-30 07:23:50.203  Error: #2  /lib/arm-linux-gnueabihf/libc.so.6 :  + 0x2a910 [0xb6ae8910]
domoticz        | 2021-03-30 07:23:50.203  Error: #3  /lib/arm-linux-gnueabihf/libc.so.6 :  + 0x1abe6 [0xb6ad8be6]
domoticz        | 2021-03-30 07:23:50.203  Error: #4  /lib/arm-linux-gnueabihf/libc.so.6 : gsignal + 0x79 [0xb6ae7bce]

[waltervl]

The official Domoticz Docker is currently Beta only, currently on v 13133 : https://www.domoticz.com/wiki/Docker

[pvklink]

Thanks @waltervl !
That is the right image for me!
I played a lot with docker last days, and with the below yml file (and a nodered dockerfile) i have my first setup working (a bit).
I started with a setup with IOTstack that helps you with some files and commands...

Already have these applications working
- domoticz (with hue, broadlink, zwave and rfxcom and dzvents scripts, and databaseoutside the container)
- mqtt (with nodered and domoticz, must still test this)
- nodered, with flows outside of the container

For those who want to have a first startup, see my yml below
For others, if you can check my yml file, i think there are still a number of entries that arent needed.
Part i did some guessing was the network part, dont now if this is the right setup for letting these 3 applications talk together

Code: Select all

version: '3.6'
services:
  domoticz:
    container_name: domoticz
    image: domoticz/domoticz:latest
    ports:
    - "82:8080"
    - "6144:6144"
    - "1443:1443"
    - "9000:9000"
    devices:
    - '/dev/ttyUSB0:/dev/ttyUSB0'
    - /dev/ttyACM0:/dev/ttyACM0
    volumes:
    - ./volumes/domoticz/data:/opt/domoticz/userdata
    restart: unless-stopped
    network_mode: bridge
    environment:
    - PUID=1000
    - PGID=1000
    #- LOG_PATH=/opt/domoticz/userdata/domoticz.log
  mosquitto:
    container_name: mosquitto
    image: eclipse-mosquitto
    restart: unless-stopped
    user: "1000"
    ports:
    - "1883:1883"
    volumes:
    - ./volumes/mosquitto/data:/mosquitto/data
    - ./volumes/mosquitto/log:/mosquitto/log
    - ./volumes/mosquitto/pwfile:/mosquitto/pwfile
    - ./services/mosquitto:/mosquitto/config:ro
    network_mode: bridge
  nodered:
    container_name: nodered
    build: ./services/nodered/.
    restart: unless-stopped
    user: "0"
    privileged: true
    environment:
      - TZ=Etc/UTC
    ports:
      - "1880:1880"
    volumes:
      - "./volumes/nodered/data:/data"
      - "/var/run/docker.sock:/var/run/docker.sock"
      - "/var/run/dbus/system_bus_socket:/var/run/dbus/system_bus_socket"
    devices:
      - "/dev/gpiomem:/dev/gpiomem"
      - "/dev/ttyAMA0:/dev/ttyAMA0"
      - "/dev/vcio:/dev/vcio"
    networks:
      - iotstack_nw
    logging:
      options:
        max-size: 5m
        max-file: "3"
networks:
  iotstack_nw:
    name: IOTstack_Net
    # external: true
    driver: bridge
    ipam:
      driver: default
      config:
        - subnet: 10.77.60.0/24

and my dockerfile for nodered (to add some extra nodes)

Code: Select all

FROM nodered/node-red:latest-12
USER root
RUN apk update && apk add --no-cache eudev-dev
USER node-red

RUN cd /usr/src/node-red && npm install --save node-red-configurable-ping node-red-dashboard node-red-node-random node-red-node-email 

[waltervl]

Good it works!
A quick question: Do you use DzVents scripts from the internal event system?
I am playing with Docker too but getting errors when saving a DzVents script.

[pvklink]

I only use DZvents, and my scripts are stored in the database, so thats easy when using docker and having the database outside the container, that part works great!

I got everything working except the Broadlink RM2 with kodi remote plugin.
I think this plugin is not prepared for docker.