It did. I don’t even use AppArmor. Still, here’s the error I get when launching the Teamspeak container:
docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: unable to apply apparmor profile: apparmor failed to apply profile: write /proc/self/attr/apparmor/exec: no such file or directory: unknown.
This is how I start the container:
docker run -d --name TeamSpeak3_Server -e TS_UPDATE=1 -e TIME_ZONE=Europe/Berlin -p 9987:9987/udp -p 10011:10011/tcp -p 30033:30033/tcp --restart=unless-stopped -v /terra/teamspeak3-server/:/teamspeak/save/ ertagh/teamspeak3-server:latest-box
The mediawiki container throws the same error as teamspeak. My installation is running on a Rock Pi 4B+.
Edit: Doing some investigating, it seems the problem is happening inside the containers, which makes sense because as mentioned, I never had AppArmor installed. Seeing how two images have this problem, one of which has not received any kind of update in three months, I assumed the problem is with docker itself, or rather there’s been some kind of change that necessitates changing the images in some way. Downgrading docker to 20.10.22-1 -aarch64 confirmed this suspicion.