ElMariachi2021

Hello! I have solved this issue back then. It was due to device specific/bootloader issues on the GoFlexNET I am (still!) using as a printserver. You can see how I solved it there: https://github.com/nils-werner/raspi-overlayroot/issues/7 The solution of course would work very similar, no matter if one is using Armbian, debian or Arch.

Hello! I run Armbian (just updated to version 21) from an 128GByte heavy duty SD card. I am just trying to setup searx (https://github.com/searx/searx) which is using Docker containers. One of the Docker containers won't start, throwing an error message: I searched for long, trying to find some possible solution for this issue. The most fitting seemd to be, where someone said: Yes, it's for another OS and hardware, but I found no other possible solution. So disabling apparmor through a kernel parameter, is what I am trying to achieve. I addded 'apparmor=0' to the bootenv, using armbian-config. I also updated the bootloader using armbian-config (is this necessary after updating env at all?). But: it does not work. dmesg shows the command line as: No 'apparmor=0' in there. And the initial problem with Docker remains. Can you help me please, I don't know how to go on from here .. Thanks! Edit: Btw, there was another issue which seemed to have resolved by itself, but maybe it's important: I did a dist-upgrade from 20 to 21 before. Then I rebooted and installed docker.io and docker-compose - but the docker-compose installation broke with an error, because zram/var/log was full at 49MByte used to 100%. I then uninstalled both, rebooted again, and then installed both packages again, which for some reason worked on the 2nd try ... but now I have noticed that zram/var/log is full most of the time (with no further errors so far..) Is this all right?

Hello! I wish to make my OrangePi 'failsafe' in regards of spontaneous power losses and such, so I need to have it running write protected, with writes going to a special partition or just RAM. My searches yielded an 'ancient' way to freeze the root filesystem using overlayroot, which isn't supoprted anymore (https://docs.armbian.com/User-Guide_Advanced-Features/) As I think that this kind of 'headless embedded usage' is an usual scenario for SBC running Armbian and having seen there was a method for doing so before, I assume there probably is a popular modern method for doing so, but I couldn' find it. How would I do this with the current Bullseye release on my Prange Pi Plus 2E? Or am I suppsed to use the classic kernel? Thank you!