i am currently running a OMV5 installation on a Pi3 to test every aspect before upgrading my main Pi4-OMV4 fileserver.
I just noticed an update in the latest OMV5 package:
openmediavault (5.3.3-1) unstable; urgency=low * Use /run instead of /var/run and /run/lock instead of /var/lock. * Disable the '/sharedfolder/<xyz>' feature by default on new installations because it makes too much problems. It can be enabled by setting the environment variable to 'OMV_SHAREDFOLDERS_DIR_ENABLED="YES"'. Finally run the command 'omv-salt stage run prepare' to apply the modified default values and 'omv-salt deploy run systemd' to create the unit files. * Issue #163: Apply hdparm.conf settings at runtime. * Issue #604: Wrong primary slave configuration for bond network interfaces. * Issue #605: Memory usage wrong in Dashboard and system information pages. -- Volker Theile <email@example.com> Sun, 16 Feb 2020 13:54:00 +0100
I am a bit confused on the second point of the changelog.
What is the problem with the /sharedfolder/<xyx> feature?
I currently use them a lot to generalize the path to my docker configuration directory.
I have one /sharedfolder/docker_config/ directory with all the various config of the containers I am running.
If /sharedfolder/ is disabled (or may be discontinued in the future altogether) what is the proper way to bind-mount configurations in docker?