containerd systemd unit started before containerd is fully ready #8468
Description
Description
This was already reported in #5109
I'm running kubeadm in a systemd unit with After=containerd.service, and sometimes get the following error:
level=fatal msg="getting status of runtime: rpc error: code = Unknown desc = server is not initialized yet"
containerd logs
containerd[2853]: time="2023-05-03T09:41:09.370125143Z" level=info msg=serving... address=/run/containerd/containerd.sock.ttrpc
containerd[2853]: time="2023-05-03T09:41:09.370188618Z" level=info msg=serving... address=/run/containerd/containerd.sock
systemd[1]: Started containerd container runtime.
containerd[2853]: time="2023-05-03T09:41:09.430108908Z" level=info msg="containerd successfully booted in 0.345311s"
containerd[2853]: time="2023-05-03T09:41:09.430325341Z" level=info msg="Start subscribing containerd event"
containerd[2853]: time="2023-05-03T09:41:09.450471617Z" level=info msg="Start recovering state"
containerd[2853]: time="2023-05-03T09:41:10.419322678Z" level=info msg="Start event monitor"
containerd[2853]: time="2023-05-03T09:41:10.420005372Z" level=info msg="Start snapshots syncer"
containerd[2853]: time="2023-05-03T09:41:10.420028803Z" level=info msg="Start cni network conf syncer for default"
containerd[2853]: time="2023-05-03T09:41:10.420039435Z" level=info msg="Start streaming server"
Describe the results you received and expected
containerd should tell systemd it's ready to handle every commands without error
What version of containerd are you using?
1.7.0
Any other relevant information
No response
Show configuration if it is related to CRI plugin.
No response