OMV6 reboots when applying configuration change

Hi,

When applying any configuration change, omv reboot!? Is-It normal?

For example, if I update my nfs share config, save, then apply new config, the cpu process to finally have “504 - Gateway Time-out” error message then after few seconds omv reboot.

And after reboot, new config is applied…. but docker containers are stopped.

Same behavior when applying omv update (sudo omv-upgrade).

I never notice this with previous version.

I’m running OMV6.4.5-1 through Pi3 with usage of Samba & Nfs shares and omv extra/docker.

If somebody has an idea….

I'm fully agree with the possibility of RAM issue. Maybe also the SD; I boot from usb slot with an SD card adaptor and SD is quite old.

kriss@OMVPi:~ $ sudo omv-salt deploy run nfs

OMVPi:

----------

ID: configure_default_nfs-kernel-server

Function: file.managed

Name: /etc/default/nfs-kernel-server

Result: True

Comment: File /etc/default/nfs-kernel-server is in the correct state

Started: 10:01:14.639069

Duration: 376.565 ms

Changes:

----------

ID: configure_nfsd_exports

Function: file.managed

Name: /etc/exports

Result: True

Comment: File /etc/exports is in the correct state

Started: 10:01:15.016400

Duration: 372.134 ms

Changes:

----------

ID: start_rpc_statd_service

Function: service.running

Name: rpc-statd

Result: True

Comment: The service rpc-statd is already running

Started: 10:01:15.586571

Duration: 230.002 ms

Changes:

----------

ID: start_nfs_server_service

Function: service.running

Name: nfs-server

Result: True

Comment: The service nfs-server is already running

Started: 10:01:15.821051

Duration: 155.924 ms

Changes:

Summary for OMVPi

------------

Succeeded: 4

Failed: 0

------------

Total states run: 4

Total run time: 1.135 s

I finally reinstall docker (with compose 6.8), and it seems to be stable....

Maybe something wrong occurs during previous installation with 6.7 compose; Let's check in coming days.

I've got one question for you concerning new docker compose.

How is manage the log ?

And in particular the size, shall we need to specify a size limitation for our container yaml ?

I ask this because I remind I met an issue where logs fill the SD using OMV4 & docker

Thank you for your help.