what happen if you try to restart the service
systemctl restart containerd.service
systemctl restart containerd.service
It pegged Core 1 at 100% and then result:
Job for containerd.service failed because a timeout was exceeded.
See "systemctl status containerd.service" and "journalctl -xeu containerd.service" for details.
systemctl status containerd.service
containerd.service - containerd container runtime
Loaded: loaded (/lib/systemd/system/containerd.service; enabled; preset: enabled)
Active: activating (start) since Thu 2023-08-03 17:16:28 EDT; 34s ago
Docs: https://containerd.io
Process: 17262 ExecStartPre=/sbin/modprobe overlay (code=exited, status=0/SUCCESS)
Main PID: 17263 (containerd)
Tasks: 6
Memory: 18.5M
CPU: 22.100s
CGroup: /system.slice/containerd.service
└─17263 /usr/bin/containerd
Aug 03 17:16:55 DietPi containerd[17263]: k8s.io/apimachinery/pkg/apis/meta/v1.sovGenerated(...)
Aug 03 17:16:55 DietPi containerd[17263]: /go/src/github.com/containerd/containerd/vendor/google.golang.org/protobuf/internal/strs/strings_unsafe.go:-6211
Aug 03 17:16:55 DietPi containerd[17263]: k8s.io/apimachinery/pkg/apis/meta/v1.sovGenerated(...)
Aug 03 17:16:55 DietPi containerd[17263]: /go/src/github.com/containerd/containerd/vendor/google.golang.org/protobuf/internal/strs/strings_unsafe.go:-6211
Aug 03 17:16:55 DietPi containerd[17263]: k8s.io/apimachinery/pkg/apis/meta/v1.sovGenerated(...)
Aug 03 17:16:55 DietPi containerd[17263]: /go/src/github.com/containerd/containerd/vendor/google.golang.org/protobuf/internal/strs/strings_unsafe.go:-6211
Aug 03 17:16:55 DietPi containerd[17263]: k8s.io/apimachinery/pkg/apis/meta/v1.sovGenerated(...)
Aug 03 17:16:55 DietPi containerd[17263]: /go/src/github.com/containerd/containerd/vendor/google.golang.org/protobuf/internal/strs/strings_unsafe.go:-6211
Aug 03 17:16:55 DietPi containerd[17263]: k8s.io/apimachinery/pkg/apis/meta/v1.sovGenerated(...)
Aug 03 17:16:55 DietPi containerd[17263]: /go/src/github.com/containerd/containerd/vendor/google.golang.org/protobuf/internal/strs/strings_unsafe.go:-6211
journalctl -xeu containerd.service
result is similar to my previous journalctl post, it repeats until it fills the terminal history buffer
Aug 03 17:19:55 DietPi containerd[17371]: /go/src/github.com/containerd/containerd/vendor/google.golang.org/protobuf/internal/strs/strings_unsafe.go:-6211
Aug 03 17:19:55 DietPi containerd[17371]: k8s.io/apimachinery/pkg/apis/meta/v1.sovGenerated(...)
Aug 03 17:19:55 DietPi containerd[17371]: /go/src/github.com/containerd/containerd/vendor/google.golang.org/protobuf/internal/strs/strings_unsafe.go:-6211
Aug 03 17:19:55 DietPi containerd[17371]: k8s.io/apimachinery/pkg/apis/meta/v1.sovGenerated(...)
Aug 03 17:19:55 DietPi containerd[17371]: /go/src/github.com/containerd/containerd/vendor/google.golang.org/protobuf/internal/strs/strings_unsafe.go:-6211
Aug 03 17:19:55 DietPi containerd[17371]: k8s.io/apimachinery/pkg/apis/meta/v1.sovGenerated(...)
Aug 03 17:19:55 DietPi containerd[17371]: /go/src/github.com/containerd/containerd/vendor/google.golang.org/protobuf/internal/strs/strings_unsafe.go:-6211
Just an update to say I watched htop for a while and systemd-journald was at 100% cpu for at least an hour. I uninstalled docker and it immediately went to 0.
Once docker is installed and the system rebooted, docker is not starting, but it is keeping the logs busy.
hmm you could try to reinstall containerd.io package
apt install --reinstall containerd.io
try to reinstall containerd.io
No change. I also tried a reinstall of docker using dietpi-software and no fix.
I tried to restore a backup from a week ago, but it also had docker+portainer on it (it also didn’t work). At the time of the backup I wasn’t actively using docker, so I hadn’t encountered this issue.
I may try a fresh Dietpi install if I have time on the weekend.
Thanks for your help @Joulinar . I will update here if I discover anything.
Just an update if this thread comes up in a search: a new install of DietPi was required. All I can think is that (as was mentioned) something got corrupted in the filesystem. Unfortunately, I had an unrelated crash that wiped out my sdcard, so a complete reinstall from ISO was required. After that, a restored backup put me back at zero. Still no docker and I’m sort of afraid to install it now.
Probably backup data already corrupted and you restore the issue 
You are likely right, but I needed it working for now. I will reassess at a later time. Thanks for your help and suggestions!
Docker, compose, and portainer are now running on this Pi, using the same restored backup. Whatever was wrong in the filesystem was fixed by the reinstall. Just an FYI.
1 Like
good you are back online. 
1 Like