Hello,
following today’s update, my Gladys did not restart (I have the restart=always option) this time and it’s the first time this has happened.
In my Watchtower messages, I got this:
And Portainer shows that the Gladys Docker container is just created:
For info, I don’t have a Zigbee USB dongle connected, I’m using a remote SMLIGHT.
I’m on Proxmox with an LXC Docker container.
EDIT: And I can’t start it,
No issues on my end, restart completed successfully.
argh, still haven’t managed to restart the thing 
Quick note to let you know that Gladys is running again 
After several checks on my Proxmox cluster, I couldn’t get the gladys container to restart. However, the implicated directory /dev/serial/by-id/ does exist and is owned by root:root; this directory is empty inside.
I then moved the gladys LXC to another machine in my cluster and everything restarted without issue.
Looking more closely at the difference, on my Proxmox cluster (HA + Ceph) I have 2 USB keys (Zwave and RF433-) in resource mappings plugged into the first machine and directed to it. My Jeedom VM (which is also on it) manages and accesses these 2 USB keys.
This is the machine where I also had Gladys.
On my second machine (where I moved Gladys), I don’t have any keys in resource mappings.
