Hi
I'm playing with the new OCI container feature, and is trying to get Frigate running.
I have the image booting and running, but after a few seconds, Frigate complaining about:
a "df -h" reveals that /dev is full
I have tried to edit the fstab file and do a remount, which works, but the fstab file is emptied with a reboot of the container.
What would be my next course of action?
A second note, Frigate can not apply configuration changes without a reboot, so it has a "Save and reboot" feature. However, the reboot, initiated from within, causes the container to halt/power off.
/Lars
I'm playing with the new OCI container feature, and is trying to get Frigate running.
I have the image booting and running, but after a few seconds, Frigate complaining about:
Code:
s6-log: warning: unable to write to /dev/shm/logs/frigate/current: No space left on device
s6-log: warning: unable to write to /dev/shm/logs/nginx/current: No space left on devicea "df -h" reveals that /dev is full
Code:
root@frigate01:~# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/pve-vm--100--disk--0 59G 2.9G 54G 6% /
/dev/mapper/pve-vm--100--disk--1 295G 2.1M 280G 1% /media/frigate
/dev/mapper/pve-vm--100--disk--2 7.8G 2.3M 7.4G 1% /config
none 492K 492K 0 100% /dev
udev 3.8G 0 3.8G 0% /dev/ttyI have tried to edit the fstab file and do a remount, which works, but the fstab file is emptied with a reboot of the container.
What would be my next course of action?
A second note, Frigate can not apply configuration changes without a reboot, so it has a "Save and reboot" feature. However, the reboot, initiated from within, causes the container to halt/power off.
/Lars