Closed hille721 closed 1 year ago
Can you share a bit more information? Have you had a look at for example #64
I'm running deconz with podman, controlled by following systemd service:
[Unit]
Description=Podman container-deconz.service
Documentation=man:podman-generate-systemd(1)
Wants=network-online.target
After=network-online.target
RequiresMountsFor=%t/containers
[Service]
Environment=PODMAN_SYSTEMD_UNIT=%n
Restart=always
TimeoutStopSec=70
ExecStartPre=/bin/rm -f %t/%n.ctr-id
ExecStart=/usr/bin/podman run --cidfile=%t/%n.ctr-id --cgroups=no-conmon --rm --sdnotify=conmon --replace -d -p 8080:8080 -p 8443:8443 -p 5905:5900 -p 6080:6080 --name=deconz -v /etc/localtime:/etc/localtime:ro -v /srv/deconz:/opt/deCONZ --device=/dev/ttyACM0 -e DECONZ_DEVICE=/dev/ttyACM0 -e DECONZ_WEB_PORT=8080 -e DECONZ_WS_PORT=8443 -e TZ=UTC -e DECONZ_VNC_MODE=1 deconzcommunity/deconz:stable
ExecStop=/usr/bin/podman stop --ignore --cidfile=%t/%n.ctr-id
ExecStopPost=/usr/bin/podman rm -f --ignore --cidfile=%t/%n.ctr-id
Type=notify
NotifyAccess=all
[Install]
WantedBy=default.target
This worked for over ~ a year, but suddenly it did not start anymore. First I thought it might be related to my deCONZ update to 2.19.03, but error is now also comming for the 2.18 image.
Already removed /opt/deCONZ/vnc, but error was still coming.
The issue you mentioned seems to be not really related to my one, because I had it already running
ok funny, just retried it again. Those tigervnc error messages are still there, but now the container starts and deconz, phoscon and VNC are working.
Thus I close this issue.
When setting
-e DECONZ_VNC_MODE=1
the container crashs during startup. With VNCs mode disabled, everything works fine. Here the logs with-e DECONZ_START_VERBOSE=0
: