3·
1 year agoYou can host docker volumes over NFS, but the actual container images need to exist on a filesystem that supports overlay (which NFS does not) unless you want things to be slow as shit. And I really do mean miserably slow. A container image shared over NFS will take forever to spin up because it has to duplicate the entire container filesystem instead of using overlays, and then it’ll blow up your disk usage by copying all these files around instead of overlaying them. It’s truly unusable.
Looks like you’ve already had some help fixing your system. I’d recommend reading the arch wiki pages on encryption. Even if you’re not running arch, the wiki is a good source of up-to-date information, and contains many practical tips.
This section about setting up your
/etc/crypttabto unlock a non-root filesystem at boot might be useful. Even if you don’t want to unlock at boot, it explains how crypttab works: https://wiki.archlinux.org/title/Dm-crypt/System_configuration#crypttab.There’s another useful section if you want to decrypt on demand after boot: https://wiki.archlinux.org/title/Dm-crypt/System_configuration#Mounting_on_demand
Lastly, if you’re experimenting with fstab entries for a non-root device, consider setting
nofailso that if you screw anything up the system still boots. This section is somewhat relevant: https://wiki.archlinux.org/title/Fstab#External_devicesBasically, you need both a crypttab entry and an fstab entry to open and then mount the device.