Creating a bug report/issue
Required Information
-
DietPi version |
cat /boot/dietpi/.version
G_DIETPI_VERSION_CORE=8
G_DIETPI_VERSION_SUB=15
G_DIETPI_VERSION_RC=2
G_GITBRANCH=‘master’
G_GITOWNER=‘MichaIng’ -
Distro version |
echo $G_DISTRO_NAME $G_RASPBIAN
bullseye -
Kernel version |
uname -a
Linux Seth 5.10.0-20-amd64 #1 SMP Debian 5.10.158-2 (2022-12-13) x86_64 GNU/Linux -
SBC model |
echo $G_HW_MODEL_NAMEor (EG: RPi3)
Virtual Machine (x86_64)
Additional Information (if applicable)
-
Software title | Docker
-
Was the software title installed freshly or updated/migrated?
Updated -
Can this issue be replicated on a fresh installation of DietPi?
Probably not. -
Bug report ID | c060fcd2-b63c-45c2-bb43-6264287b278e
Actual behaviour
After doing a dietpi-update Docker and the containers stops working and even after re-installing Docker won’t work. During the installation I get error messages that prevent me to install Docker.
Digest:
?? sha256:9fa1ec78b4e29d83593cf9720674b72829c9cdc0db7083a962bc30e64e27f64e
?? Status: Downloaded newer image for portainer/portainer-ce:latest
?? 4e244f7247fd652df29f5a995897acafd73ef409cb4480ad04430d6a9fccfed0
?? 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.
I’ve never met anything like this and I don’t want to completely reinstall the entire Dietpi bc of Docker. Any help would be appriciated!