Marc-Berg
commented
1 week ago Unfortunately, I've only just seen the issue. I could imagine that the behavior is related to the fact that symbolic links are not handled correctly. Try adding the “bind” parameter.
UUID=351b005a-a268-4417-972c-e4106351e298 /var/lib/docker/volumes/ ext4 defaults,auto,users,rw,nofail,bind 0 0
Description / Beschreibung
System: Pi CM4 (32G eMMC, 8G RAM) on a Waveshare IO Bord with PCIe Interface. NVMe SSD attached to PCIe Interface. NVMe contains 1 Ext4-partition ("nvme0n1p1"), where all docker volumes are stored. Running Raspberry OS lite (bookworm) Docker Image 10.0.0 NodeJS: 20.18.0 NPM: 10.8.2
On the docker system, several containers are running, e.g. iobroker, zigbee2mqtt, mosquitto, rasspberrymatic, pihole, portainer, homeassistant
When all the containers were set up, their volumes were located at /var/lib/docker/volumes which was initially at the eMMC. Since the volumes meed nore memory, I deceided to attach a NVMe SSD via the PCIe port.
Process of migration:
Result: all Containers restarted successfully.
To automount the NVMe at Startup I added a line in the /etc/fstab file. UUID=351b005a-a268-4417-972c-e4106351e298 /var/lib/docker/volumes/ ext4 defaults,auto,users,rw,nofail 0 0
After a reboot of the system, the mount works in general. All containers can be started and find the data in their volumes, but iobroker stucks in a Startup loop, with the error: Connecting to database: Permissionn denied.
When I do de mount manually (stopping docker, umount, mount with sudo mount /dev/nvme0n1p1 /var/lib/docker/volumes, start docker), iobroker starts up regular.
I have no idea what might be the difference in the two ways of mounting the NVMe.
Image version
V10.0.0
Docker logs / Docker Protokoll