# After dietpi update docker does not start
**URL:** https://dietpi.com/forum/t/after-dietpi-update-docker-does-not-start/15826
**Category:** General Discussion
**Tags:** services
**Created:** [3 February 2023 11:53 UTC](https://dietpi.com/forum/t/after-dietpi-update-docker-does-not-start/15826 "2023-02-03T11:53:45Z")
**Posts on this page:** 17
**Page:** 1
### Author:  [@drunKnight](https://dietpi.com/forum/u/drunKnight)
#### Post date: [3 February 2023 11:53 UTC](https://dietpi.com/forum/t/after-dietpi-update-docker-does-not-start/15826/1 "2023-02-03T11:53:46Z")
Hope that someone can help me. I updated my raspberry pi 4 with dietpi-update and docker does not start again.
Here is the service logs:
```auto
Feb 03 11:26:45 DietPi dockerd[462]: time="2023-02-03T11:26:45.228754882Z" level=error msg="[graphdriver] prior storage driver devicemapper is deprecated and will be removed in a future release; update the the daemon configuration and explicitly choose this storage driver to continue using it; visit https://docs.docker.com/go/storage-driver/
for more information"
Feb 03 11:26:45 DietPi dockerd[462]: failed to start daemon: error initializing graphdriver: prior storage driver devicemapper is deprecated and will be removed in a future release; update the the daemon configuration and explicitly choose this storage driver to continue using it; visit https://docs.docker.com/go/storage-driver/ for more inf
ormation
Feb 03 11:26:45 DietPi systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Feb 03 11:26:45 DietPi systemd[1]: docker.service: Failed with result 'exit-code'.
Feb 03 11:26:47 DietPi systemd[1]: docker.service: Service RestartSec=2s expired, scheduling restart.
Feb 03 11:26:47 DietPi systemd[1]: docker.service: Scheduled restart job, restart counter is at 1.
Feb 03 11:26:47 DietPi systemd[1]: Stopped Docker Application Container Engine.
Feb 03 11:26:47 DietPi systemd[1]: Started Docker Application Container Engine.
Feb 03 11:26:47 DietPi dockerd[581]: time="2023-02-03T11:26:47.919622473Z" level=warning msg="Usage of loopback devices is strongly discouraged for production use. Please use `--storage-opt dm.thinpooldev` or use `man dockerd` to refer to dm.thinpooldev section." storage-driver=devicemapper
Feb 03 11:26:48 DietPi dockerd[581]: time="2023-02-03T11:26:48.055395917Z" level=warning msg="Base device already exists and has filesystem ext4 on it. User specified filesystem will be ignored." storage-driver=devicemapper
Feb 03 11:26:48 DietPi dockerd[581]: time="2023-02-03T11:26:48.135999824Z" level=error msg="[graphdriver] prior storage driver devicemapper is deprecated and will be removed in a future release; update the the daemon configuration and explicitly choose this storage driver to continue using it; visit https://docs.docker.com/go/storage-driver/
for more information"
Feb 03 11:26:48 DietPi dockerd[581]: failed to start daemon: error initializing graphdriver: prior storage driver devicemapper is deprecated and will be removed in a future release; update the the daemon configuration and explicitly choose this storage driver to continue using it; visit https://docs.docker.com/go/storage-driver/ for more inf
ormation
Feb 03 11:26:48 DietPi systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Feb 03 11:26:48 DietPi systemd[1]: docker.service: Failed with result 'exit-code'.
Feb 03 11:26:50 DietPi systemd[1]: docker.service: Service RestartSec=2s expired, scheduling restart.
Feb 03 11:26:50 DietPi systemd[1]: docker.service: Scheduled restart job, restart counter is at 2.
Feb 03 11:26:50 DietPi systemd[1]: Stopped Docker Application Container Engine.
Feb 03 11:26:50 DietPi systemd[1]: Started Docker Application Container Engine.
Feb 03 11:26:50 DietPi dockerd[599]: time="2023-02-03T11:26:50.746280045Z" level=warning msg="Usage of loopback devices is strongly discouraged for production use. Please use `--storage-opt dm.thinpooldev` or use `man dockerd` to refer to dm.thinpooldev section." storage-driver=devicemapper
Feb 03 11:26:50 DietPi dockerd[599]: time="2023-02-03T11:26:50.885199267Z" level=warning msg="Base device already exists and has filesystem ext4 on it. User specified filesystem will be ignored." storage-driver=devicemapper
Feb 03 11:26:50 DietPi dockerd[599]: time="2023-02-03T11:26:50.956943563Z" level=error msg="[graphdriver] prior storage driver devicemapper is deprecated and will be removed in a future release; update the the daemon configuration and explicitly choose this storage driver to continue using it; visit https://docs.docker.com/go/storage-driver/
for more information"
Feb 03 11:26:50 DietPi dockerd[599]: failed to start daemon: error initializing graphdriver: prior storage driver devicemapper is deprecated and will be removed in a future release; update the the daemon configuration and explicitly choose this storage driver to continue using it; visit https://docs.docker.com/go/storage-driver/ for more inf
ormation
```
Can someone help please?
---
### Author:  [@Joulinar](https://dietpi.com/forum/u/Joulinar)
#### Post date: [3 February 2023 12:06 UTC](https://dietpi.com/forum/t/after-dietpi-update-docker-does-not-start/15826/2 "2023-02-03T12:06:15Z")
> [@drunKnight](#):
>
> `error msg="[graphdriver] prior storage driver devicemapper is deprecated`
looks like something related to storage driver. Can you check if there was anything set specifically?
```auto
cat /etc/docker/daemon.json
```
---
### Author:  [@drunKnight](https://dietpi.com/forum/u/drunKnight)
#### Post date: [3 February 2023 13:59 UTC](https://dietpi.com/forum/t/after-dietpi-update-docker-does-not-start/15826/3 "2023-02-03T13:59:35Z")
```auto
{
"data-root": "/mnt/dietpi_userdata/docker-data",
"log-driver": "journald",
"log-level": "warn",
"debug": false
}
```
Does this mean anything? Everything was working fine before the update
---
### Author:  [@drunKnight](https://dietpi.com/forum/u/drunKnight)
#### Post date: [3 February 2023 14:28 UTC](https://dietpi.com/forum/t/after-dietpi-update-docker-does-not-start/15826/4 "2023-02-03T14:28:15Z")
So I think I found the problem.
For Dietpi version _v8.13.2_ docker version is _23.0.0, build e92dd87_.
If you check the engine deprecation features in [Docker documentation](https://docs.docker.com/engine/deprecated/) you can see that Device mapper storage driver was disabled in this version (more details [here](https://docs.docker.com/engine/deprecated/#device-mapper-storage-driver)).
So to force this driver I just added the line:
```auto
"storage-driver": "devicemapper"
```
in `/etc/docker/daemon.json`
But now the documentation says that I should migrate to `overlay2`. I still don’t know how to do this.
---
### Author:  [@Joulinar](https://dietpi.com/forum/u/Joulinar)
#### Post date: [3 February 2023 15:53 UTC](https://dietpi.com/forum/t/after-dietpi-update-docker-does-not-start/15826/5 "2023-02-03T15:53:33Z")
> [@drunKnight](#):
>
> For Dietpi version _v8.13.2_ docker version is _23.0.0, build e92dd87_.
Docker version has nothing to do with DietPi version. Docker is an own software title installed via `apt` package manager. What happen, during DietPi update we force an `apt` package update as well. Therefore, new Docher version has been installed in parallel.
Usually, `overlay2` should be the default nowadays. Not sure why your system is running `devicemapper`. Maybe due to historical reason?
Not sure if there is a direct way to move from `devicemapper` to `overlay2`. In worst case, this would mean to drop all images and container, set `overlay2` and recreate all container.
---
### Author:  [@cenizo](https://dietpi.com/forum/u/cenizo)
#### Post date: [4 February 2023 07:54 UTC](https://dietpi.com/forum/t/after-dietpi-update-docker-does-not-start/15826/6 "2023-02-04T07:54:11Z")
The same thing happens to me and if I do a docker ps I only get 1 docker out of the 30 that I have
```auto
apt --fix-broken install
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
linux-image-5.10.0-21-amd64
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 318 MB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 72244 files and directories currently installed.)
Removing linux-image-5.10.0-21-amd64 (5.10.162-1) ...
/etc/kernel/postrm.d/initramfs-tools:
update-initramfs: Deleting /boot/initrd.img-5.10.0-21-amd64
/etc/kernel/postrm.d/zz-update-grub:
/usr/sbin/grub-mkconfig: 9: /etc/default/grub: splash: not found
run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 127
dpkg: error processing package linux-image-5.10.0-21-amd64 (--remove):
installed linux-image-5.10.0-21-amd64 package post-removal script subprocess returned error exit status 1
dpkg: too many errors, stopping
Errors were encountered while processing:
linux-image-5.10.0-21-amd64
Processing was halted because there were too many errors.
E: Sub-process /usr/bin/dpkg returned an error code (1)
```
---
### Author:  [@Joulinar](https://dietpi.com/forum/u/Joulinar)
#### Post date: [4 February 2023 07:56 UTC](https://dietpi.com/forum/t/after-dietpi-update-docker-does-not-start/15826/7 "2023-02-04T07:56:10Z")
> [@cenizo](#):
>
> ```auto
> /etc/kernel/postrm.d/zz-update-grub:
> /usr/sbin/grub-mkconfig: 9: /etc/default/grub: splash: not found
> run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 127
>
> ```
@cenizo your issue seems to be unrelated. The error above is pointing into issues to finalize the kernel update. @MichaIng can you have a look.
---
### Author:  [@cenizo](https://dietpi.com/forum/u/cenizo)
#### Post date: [4 February 2023 10:17 UTC](https://dietpi.com/forum/t/after-dietpi-update-docker-does-not-start/15826/8 "2023-02-04T10:17:44Z")
I also updated dietpi and since then no docker starts, I show the error.
```auto
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
```
If I do a docker ps it only shows me 1 of the 30 dockers that I have
---
### Author:  [@Joulinar](https://dietpi.com/forum/u/Joulinar)
#### Post date: [4 February 2023 10:39 UTC](https://dietpi.com/forum/t/after-dietpi-update-docker-does-not-start/15826/9 "2023-02-04T10:39:09Z")
This has nothing to do with DietPi. Docker 5.23 has some challenges [DietPi-Software | Docker: Service fails to start after upgrade (AppArmor) · Issue #6126 · MichaIng/DietPi · GitHub](https://github.com/MichaIng/DietPi/issues/6126)
> **[Docker Engine 23.0 release notes](https://docs.docker.com/engine/release-notes/23.0/#known-issues)**
>
> Learn about the new features, bug fixes, and breaking changes for Docker Engine
---
### Author:  [@nikos73](https://dietpi.com/forum/u/nikos73)
#### Post date: [5 February 2023 15:38 UTC](https://dietpi.com/forum/t/after-dietpi-update-docker-does-not-start/15826/10 "2023-02-05T15:38:08Z")
I too have a problem with docker/portainer, as they don’t start. I think it happened after the latest-recent apt update of docker and not after the upgrade of DietPi, which was several days before.
From my logs, it seems that I have the apparmor problem:
```auto
root@DietPi:~# journalctl -u docker -u containerd
-- Journal begins at Sun 2023-02-05 17:20:55 EET, ends at Sun 2023-02-05 17:25:49 EET. --
Feb 05 17:20:57 DietPi systemd[1]: Starting containerd container runtime...
Feb 05 17:20:58 DietPi containerd[514]: time="2023-02-05T17:20:58+02:00" level=warning msg="containerd config version `1` has been deprecated and will be removed in containerd v2.0, please switch to version `2`, see https://github.com/containerd/containerd/blob/94934e1a478c20ba844d1963ba3a8580ebaf763f/docs/PLUGINS.md#version-header"
Feb 05 17:20:58 DietPi containerd[514]: time="2023-02-05T17:20:58.229595234+02:00" level=warning msg="failed to load plugin io.containerd.snapshotter.v1.devmapper" error="devmapper not configured"
Feb 05 17:20:58 DietPi containerd[514]: time="2023-02-05T17:20:58.231738065+02:00" level=warning msg="could not use snapshotter devmapper in metadata plugin" error="devmapper not configured"
Feb 05 17:20:58 DietPi containerd[514]: time="2023-02-05T17:20:58.241290129+02:00" level=error msg="failed to initialize a tracing processor \"otlp\"" error="no OpenTelemetry endpoint: skip plugin"
Feb 05 17:20:58 DietPi systemd[1]: Started containerd container runtime.
Feb 05 17:20:59 DietPi systemd[1]: Started Docker Application Container Engine.
Feb 05 17:20:59 DietPi dockerd[634]: time="2023-02-05T17:20:59.799064067+02:00" level=error msg="AppArmor enabled on system but the docker-default profile could not be loaded: running `apparmor_parser apparmor_parser --version` failed with output: \nerror: exec: \"apparmor_parser\": executable file not found in $PATH"
Feb 05 17:21:01 DietPi dockerd[634]: time="2023-02-05T17:21:01.076056093+02:00" level=error msg="0eaef5d6bfd3a0278e168dd15eda681d789f5c7a940b700194e818ede018a4f5 cleanup: failed to delete container from containerd: no such container"
Feb 05 17:21:01 DietPi dockerd[634]: time="2023-02-05T17:21:01.076116904+02:00" level=error msg="failed to start container" container=0eaef5d6bfd3a0278e168dd15eda681d789f5c7a940b700194e818ede018a4f5 error="AppArmor enabled on system but the docker-default profile could not be loaded: running `apparmor_parser apparmor_parser --version` failed with output: \nerror: exec: \"apparmor_parser\": executable file not found in $PATH"
Feb 05 17:21:01 DietPi dockerd[634]: time="2023-02-05T17:21:01.165650135+02:00" level=error msg="c607f3656942440b7c03faa4ff42a61029ec6723b3eb77c94d5bf6bfcd381519 cleanup: failed to delete container from containerd: no such container"
Feb 05 17:21:01 DietPi dockerd[634]: time="2023-02-05T17:21:01.165702125+02:00" level=error msg="failed to start container" container=c607f3656942440b7c03faa4ff42a61029ec6723b3eb77c94d5bf6bfcd381519 error="AppArmor enabled on system but the docker-default profile could not be loaded: running `apparmor_parser apparmor_parser --version` failed with output: \nerror: exec: \"apparmor_parser\": executable file not found in $PATH"
Feb 05 17:21:01 DietPi dockerd[634]: time="2023-02-05T17:21:01.180188444+02:00" level=error msg="5dfef709f5d164c632dd4c7a4a2026bf07d3d5a8a6af55e95a4d30a3741d8ecd cleanup: failed to delete container from containerd: no such container"
Feb 05 17:21:01 DietPi dockerd[634]: time="2023-02-05T17:21:01.180483191+02:00" level=error msg="failed to start container" container=5dfef709f5d164c632dd4c7a4a2026bf07d3d5a8a6af55e95a4d30a3741d8ecd error="AppArmor enabled on system but the docker-default profile could not be loaded: running `apparmor_parser apparmor_parser --version` failed with output: \nerror: exec: \"apparmor_parser\": executable file not found in $PATH"
Feb 05 17:21:01 DietPi dockerd[634]: time="2023-02-05T17:21:01.270447785+02:00" level=error msg="75ccd5448774bfc12bf76d47cdd244f7c9c6697ddff9629ae4cf1c02fae5a4e7 cleanup: failed to delete container from containerd: no such container"
```
Should I do the following:
```auto
apt install apparmor
systemctl stop apparmor
```
or is there another best-suggested solution?
For the record, it is a VM x86 AMD64
---
### Author:  [@Joulinar](https://dietpi.com/forum/u/Joulinar)
#### Post date: [5 February 2023 15:52 UTC](https://dietpi.com/forum/t/after-dietpi-update-docker-does-not-start/15826/11 "2023-02-05T15:52:21Z")
> [@nikos73](#):
>
> Should I do the following:
>
> > apt install apparmor
> > systemctl stop apparmor
Yes that’s the way forward.
---
### Author:  [@nikos73](https://dietpi.com/forum/u/nikos73)
#### Post date: [5 February 2023 16:01 UTC](https://dietpi.com/forum/t/after-dietpi-update-docker-does-not-start/15826/12 "2023-02-05T16:01:08Z")
Ok, did exactly that and docker is working again, thanks Joulinar
---
### Author:  [@WarHawk](https://dietpi.com/forum/u/WarHawk)
#### Post date: [6 February 2023 04:08 UTC](https://dietpi.com/forum/t/after-dietpi-update-docker-does-not-start/15826/13 "2023-02-06T04:08:53Z")
Should they also disable the apparmor service so it doesn’t restart on reboot?
---
### Author:  [@Joulinar](https://dietpi.com/forum/u/Joulinar)
#### Post date: [28 March 2023 19:50 UTC](https://dietpi.com/forum/t/after-dietpi-update-docker-does-not-start/15826/14 "2023-03-28T19:50:38Z")
Finally, Docker 23.0.2 has been released fixing the issue on x86 [Docker Engine 23.0 release notes](https://docs.docker.com/engine/release-notes/23.0/#2302)
---
### Author:  [@nikos73](https://dietpi.com/forum/u/nikos73)
#### Post date: [2 March 2024 09:59 UTC](https://dietpi.com/forum/t/after-dietpi-update-docker-does-not-start/15826/15 "2024-03-02T09:59:05Z")
Hello, I am still having problems with docker. I do not know if it is the same, but after updating docker will not start. I get the following error
```auto
root@DietPi:~# journalctl -u docker -u containerd
Mar 02 11:52:21 DietPi systemd[1]: Starting containerd.service - containerd container runtime...
Mar 02 11:52:22 DietPi containerd[573]: time="2024-03-02T11:52:22+02:00" level=warning msg="containerd config version `1` has been deprecated and will be removed in containerd v2.0, please switch to version `2`, see https://github.com/containerd/containerd/blob/9a2b85561acf7c4f970f947770ee5152358274c1/docs/PLUGINS.md#version-header"
Mar 02 11:52:22 DietPi containerd[573]: time="2024-03-02T11:52:22.655674806+02:00" level=warning msg="failed to load plugin io.containerd.snapshotter.v1.devmapper" error="devmapper not configured"
Mar 02 11:52:22 DietPi containerd[573]: time="2024-03-02T11:52:22.662053640+02:00" level=warning msg="could not use snapshotter devmapper in metadata plugin" error="devmapper not configured"
Mar 02 11:52:22 DietPi containerd[573]: time="2024-03-02T11:52:22.681561677+02:00" level=error msg="failed to initialize a tracing processor \"otlp\"" error="no OpenTelemetry endpoint: skip plugin"
Mar 02 11:52:22 DietPi systemd[1]: Started containerd.service - containerd container runtime.
Mar 02 11:52:22 DietPi systemd[1]: Started docker.service - Docker Application Container Engine.
Mar 02 11:52:24 DietPi dockerd[622]: fatal error: unexpected signal during runtime execution
Mar 02 11:52:24 DietPi dockerd[622]: [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x556d6edf0c]
Mar 02 11:52:24 DietPi dockerd[622]: goroutine 1 [running, locked to thread]:
Mar 02 11:52:24 DietPi dockerd[622]: runtime.throw({0x556efbcf4b?, 0x556d6ef41c?})
Mar 02 11:52:24 DietPi dockerd[622]: /usr/local/go/src/runtime/panic.go:1077 +0x40 fp=0x4000147ab0 sp=0x4000147a80 pc=0x556d711cc0
Mar 02 11:52:24 DietPi dockerd[622]: runtime.sigpanic()
Mar 02 11:52:24 DietPi dockerd[622]: /usr/local/go/src/runtime/signal_unix.go:845 +0x378 fp=0x4000147b10 sp=0x4000147ab0 pc=0x556d729fa8
Mar 02 11:52:24 DietPi dockerd[622]: runtime.writeHeapBits.flush({0x4000147b68?, 0x5570ce2990?, 0x4000147ba8?, 0x556d6e5a74?}, 0x4000147ba8?, 0x556d6e5a88?)
Mar 02 11:52:24 DietPi dockerd[622]: /usr/local/go/src/runtime/mbitmap.go:902 +0x14c fp=0x4000147b40 sp=0x4000147b20 pc=0x556d6edf0c
Mar 02 11:52:24 DietPi dockerd[622]: runtime.heapBitsSetType(0x4000194000, 0x140, 0x130, 0x556f7b25c0)
Mar 02 11:52:24 DietPi dockerd[622]: /usr/local/go/src/runtime/mbitmap.go:1086 +0x240 fp=0x4000147c00 sp=0x4000147b40 pc=0x556d6ee210
Mar 02 11:52:24 DietPi dockerd[622]: runtime.mallocgc(0x130, 0x556f7b25c0, 0x1)
Mar 02 11:52:24 DietPi dockerd[622]: /usr/local/go/src/runtime/malloc.go:1148 +0x588 fp=0x4000147c70 sp=0x4000147c00 pc=0x556d6e6158
Mar 02 11:52:24 DietPi dockerd[622]: runtime.newobject(...)
Mar 02 11:52:24 DietPi dockerd[622]: /usr/local/go/src/runtime/malloc.go:1328
Mar 02 11:52:24 DietPi dockerd[622]: runtime.mapassign(0x556f5a6220, 0x400010fb60, 0x5555555554000555?)
Mar 02 11:52:24 DietPi dockerd[622]: /usr/local/go/src/runtime/map.go:605 +0x98 fp=0x4000147d00 sp=0x4000147c70 pc=0x556d6e7bc8
Mar 02 11:52:24 DietPi dockerd[622]: google.golang.org/protobuf/internal/descfmt.init()
Mar 02 11:52:24 DietPi dockerd[622]: /root/build-deb/engine/vendor/google.golang.org/protobuf/internal/descfmt/stringer.go:108 +0x110 fp=0x4000147e00 sp=0x4000147d00 pc=0x556db08a70
Mar 02 11:52:24 DietPi dockerd[622]: runtime.doInit1(0x5570c1c170)
Mar 02 11:52:24 DietPi dockerd[622]: /usr/local/go/src/runtime/proc.go:6740 +0xd4 fp=0x4000147f30 sp=0x4000147e00 pc=0x556d722764
Mar 02 11:52:24 DietPi dockerd[622]: runtime.doInit(...)
Mar 02 11:52:24 DietPi dockerd[622]: /usr/local/go/src/runtime/proc.go:6707
Mar 02 11:52:24 DietPi dockerd[622]: runtime.main()
Mar 02 11:52:24 DietPi dockerd[622]: /usr/local/go/src/runtime/proc.go:249 +0x374 fp=0x4000147fd0 sp=0x4000147f30 pc=0x556d7147c4
Mar 02 11:52:24 DietPi dockerd[622]: runtime.goexit()
Mar 02 11:52:24 DietPi dockerd[622]: /usr/local/go/src/runtime/asm_arm64.s:1197 +0x4 fp=0x4000147fd0 sp=0x4000147fd0 pc=0x556d749564
Mar 02 11:52:24 DietPi dockerd[622]: goroutine 2 [force gc (idle)]:
Mar 02 11:52:24 DietPi dockerd[622]: runtime.gopark(0x0?, 0x0?, 0x0?, 0x0?, 0x0?)
Mar 02 11:52:24 DietPi dockerd[622]: /usr/local/go/src/runtime/proc.go:398 +0xc8 fp=0x4000070f90 sp=0x4000070f70 pc=0x556d714b68
Mar 02 11:52:24 DietPi dockerd[622]: runtime.goparkunlock(...)
Mar 02 11:52:24 DietPi dockerd[622]: /usr/local/go/src/runtime/proc.go:404
Mar 02 11:52:24 DietPi dockerd[622]: runtime.forcegchelper()
Mar 02 11:52:24 DietPi dockerd[622]: /usr/local/go/src/runtime/proc.go:322 +0xb8 fp=0x4000070fd0 sp=0x4000070f90 pc=0x556d7149c8
Mar 02 11:52:24 DietPi dockerd[622]: runtime.goexit()
Mar 02 11:52:24 DietPi dockerd[622]: /usr/local/go/src/runtime/asm_arm64.s:1197 +0x4 fp=0x4000070fd0 sp=0x4000070fd0 pc=0x556d749564
Mar 02 11:52:24 DietPi dockerd[622]: created by runtime.init.6 in goroutine 1
Mar 02 11:52:24 DietPi dockerd[622]: /usr/local/go/src/runtime/proc.go:310 +0x24
Mar 02 11:52:24 DietPi dockerd[622]: goroutine 3 [GC sweep wait]:
Mar 02 11:52:24 DietPi dockerd[622]: runtime.gopark(0x0?, 0x0?, 0x0?, 0x0?, 0x0?)
Mar 02 11:52:24 DietPi dockerd[622]: /usr/local/go/src/runtime/proc.go:398 +0xc8 fp=0x4000071760 sp=0x4000071740 pc=0x556d714b68
Mar 02 11:52:24 DietPi dockerd[622]: runtime.goparkunlock(...)
Mar 02 11:52:24 DietPi dockerd[622]: /usr/local/go/src/runtime/proc.go:404
Mar 02 11:52:24 DietPi dockerd[622]: runtime.bgsweep(0x0?)
Mar 02 11:52:24 DietPi dockerd[622]: /usr/local/go/src/runtime/mgcsweep.go:280 +0xa0 fp=0x40000717b0 sp=0x4000071760 pc=0x556d6fe940
Mar 02 11:52:24 DietPi dockerd[622]: runtime.gcenable.func1()
Mar 02 11:52:24 DietPi dockerd[622]: /usr/local/go/src/runtime/mgc.go:200 +0x28 fp=0x40000717d0 sp=0x40000717b0 pc=0x556d6f3458
Mar 02 11:52:24 DietPi dockerd[622]: runtime.goexit()
Mar 02 11:52:24 DietPi dockerd[622]: /usr/local/go/src/runtime/asm_arm64.s:1197 +0x4 fp=0x40000717d0 sp=0x40000717d0 pc=0x556d749564
Mar 02 11:52:24 DietPi dockerd[622]: created by runtime.gcenable in goroutine 1
Mar 02 11:52:24 DietPi dockerd[622]: /usr/local/go/src/runtime/mgc.go:200 +0x6c
Mar 02 11:52:24 DietPi dockerd[622]: goroutine 4 [GC scavenge wait]:
Mar 02 11:52:24 DietPi dockerd[622]: runtime.gopark(0x4000098000?, 0x556f2ec7c0?, 0x1?, 0x0?, 0x40000031e0?)
Mar 02 11:52:24 DietPi dockerd[622]: /usr/local/go/src/runtime/proc.go:398 +0xc8 fp=0x4000071f50 sp=0x4000071f30 pc=0x556d714b68
Mar 02 11:52:25 DietPi dockerd[622]: runtime.goparkunlock(...)
Mar 02 11:52:25 DietPi dockerd[622]: /usr/local/go/src/runtime/proc.go:404
Mar 02 11:52:25 DietPi dockerd[622]: runtime.(*scavengerState).park(0x5570cb1b40)
Mar 02 11:52:25 DietPi dockerd[622]: /usr/local/go/src/runtime/mgcscavenge.go:425 +0x5c fp=0x4000071f80 sp=0x4000071f50 pc=0x556d6fc20c
Mar 02 11:52:25 DietPi dockerd[622]: runtime.bgscavenge(0x0?)
Mar 02 11:52:25 DietPi dockerd[622]: /usr/local/go/src/runtime/mgcscavenge.go:653 +0x44 fp=0x4000071fb0 sp=0x4000071f80 pc=0x556d6fc754
Mar 02 11:52:25 DietPi dockerd[622]: runtime.gcenable.func2()
Mar 02 11:52:25 DietPi dockerd[622]: /usr/local/go/src/runtime/mgc.go:201 +0x28 fp=0x4000071fd0 sp=0x4000071fb0 pc=0x556d6f33f8
Mar 02 11:52:25 DietPi dockerd[622]: runtime.goexit()
Mar 02 11:52:25 DietPi dockerd[622]: /usr/local/go/src/runtime/asm_arm64.s:1197 +0x4 fp=0x4000071fd0 sp=0x4000071fd0 pc=0x556d749564
Mar 02 11:52:25 DietPi dockerd[622]: created by runtime.gcenable in goroutine 1
Mar 02 11:52:25 DietPi dockerd[622]: /usr/local/go/src/runtime/mgc.go:201 +0xac
Mar 02 11:52:25 DietPi dockerd[622]: goroutine 5 [finalizer wait]:
Mar 02 11:52:25 DietPi dockerd[622]: runtime.gopark(0x4000003860?, 0x10?, 0x98?, 0x1?, 0x556f9a6f60?)
Mar 02 11:52:25 DietPi dockerd[622]: /usr/local/go/src/runtime/proc.go:398 +0xc8 fp=0x4000070580 sp=0x4000070560 pc=0x556d714b68
Mar 02 11:52:25 DietPi dockerd[622]: runtime.runfinq()
Mar 02 11:52:25 DietPi dockerd[622]: /usr/local/go/src/runtime/mfinal.go:193 +0x108 fp=0x40000707d0 sp=0x4000070580 pc=0x556d6f2488
Mar 02 11:52:25 DietPi dockerd[622]: runtime.goexit()
Mar 02 11:52:25 DietPi dockerd[622]: /usr/local/go/src/runtime/asm_arm64.s:1197 +0x4 fp=0x40000707d0 sp=0x40000707d0 pc=0x556d749564
Mar 02 11:52:25 DietPi dockerd[622]: created by runtime.createfing in goroutine 1
Mar 02 11:52:25 DietPi dockerd[622]: /usr/local/go/src/runtime/mfinal.go:163 +0x80
Mar 02 11:52:25 DietPi systemd[1]: docker.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Mar 02 11:52:25 DietPi systemd[1]: docker.service: Failed with result 'exit-code'.
Mar 02 11:52:27 DietPi systemd[1]: docker.service: Scheduled restart job, restart counter is at 1.
```
Any help?
---
### Author:  [@Joulinar](https://dietpi.com/forum/u/Joulinar)
#### Post date: [2 March 2024 13:58 UTC](https://dietpi.com/forum/t/after-dietpi-update-docker-does-not-start/15826/16 "2024-03-02T13:58:10Z")
This issue has nothing to do with the above. Better to open a new post.
> [@nikos73](#):
>
> ```auto
> Mar 02 11:52:24 DietPi dockerd[622]: fatal error: unexpected signal during runtime execution
> Mar 02 11:52:24 DietPi dockerd[622]: [signal SIGSEGV: segmentation violatio
>
> ```
looks like data corruption, you could try to restart your whole system are reinstall Docker.
---
### Author:  [@system](https://dietpi.com/forum/u/system)
#### Post date: [31 May 2024 13:59 UTC](https://dietpi.com/forum/t/after-dietpi-update-docker-does-not-start/15826/17 "2024-05-31T13:59:08Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.