tordenflesk Posted February 5, 2023 Share Posted February 5, 2023 Unable to start docker after update, due to apparmor I used armbian-config's "edit boot-enviroment", added "extraargs=apparmor=0" and after a reboot I still get: docker start portainer Error response from daemon: AppArmor enabled on system but the docker-default profile could not be loaded: running `apparmor_parser apparmor_parser --version` failed with output: error: exec: "apparmor_parser": executable file not found in $PATH Error: failed to start containers: portainer armbianmonitor: https://paste.armbian.com/ebuburoxeh 0 Quote Link to comment Share on other sites More sharing options...
MacBreaker Posted February 6, 2023 Share Posted February 6, 2023 Yes, i also noticed that something has changed at last update.. Try: sudo apt install apparmor -y and reboot. After that it should work... 0 Quote Link to comment Share on other sites More sharing options...
Juraj Volentier Posted February 6, 2023 Share Posted February 6, 2023 Hi, I fixed with adding extraargs=apparmor=0 into armbianEnv.txt Regards 0 Quote Link to comment Share on other sites More sharing options...
tordenflesk Posted February 6, 2023 Author Share Posted February 6, 2023 Yeah, that's my problem. armbianEnv.txt appears to have no effect what-so-ever. The CloudShell2's display stopped turning on after I upgraded to OMV6 and those fixes that I've put in armbianEnv do nothing as well. There's also the issue of reboots not working... 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.