You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Writing here as had some problems enabling overlayroot.
This should work on the ubuntu image, on debian I only got the bilibop-lockfs to work but overlayroot is a lot simpler and easier.
First install overlayroot package. I setup it to read the overlayroot.conf from the boot partition and left boot partition without overlay so enabling/disabling is easy incase overlayroot-chroot doesnt work.
/boot/overlayroot.conf:
Maybe setup label for drive, but single usb drive works fine for now.
Next problem is that the configs are setup for init image, but it seems by default the generation doesn't do conversions. I added single script to do it:
generate_initramfs.sh:
This should be nothing to do with docker. Apart from docker not being able to run by default on top of overlayroot.
Testing images on ubuntu I can run ubuntu:latest with mounted volumes without any log output.
On debian image I had to install apparmor-utils first and I get the messages:
Im not getting the overlayfs: NFS export requires "redirect_dir=nofollow" on non-upper mount, falling back to nfs_export=off. but I'm not attempting anything complex.
Is problem just the logging of the overlayfs nfs export off as docker runs?
Just set the default off? echo N > /sys/module/overlay/parameters/nfs_export
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Writing here as had some problems enabling overlayroot.
This should work on the ubuntu image, on debian I only got the bilibop-lockfs to work but overlayroot is a lot simpler and easier.
First install overlayroot package. I setup it to read the overlayroot.conf from the boot partition and left boot partition without overlay so enabling/disabling is easy incase overlayroot-chroot doesnt work.
/boot/overlayroot.conf:
/etc/overlayroot.conf:
Maybe setup label for drive, but single usb drive works fine for now.
Next problem is that the configs are setup for init image, but it seems by default the generation doesn't do conversions. I added single script to do it:
generate_initramfs.sh:
Once done it should leave you with uInitrd.img-KERNEL image on boot partition, set that into the boot.script, eg rd_img=uInitrd.img-6.12.11-meson64
Beta Was this translation helpful? Give feedback.
All reactions