Containerd config version `1` has been deprecated and will be converted on each startup in containerd v2.0, use `containerd config migrate` after upgrading to containerd 2.0 to avoid conversion on startup

General
1

The following is my docker information

docker version
Client: Docker Engine - Community
Version:           26.1.4
API version:       1.45
Go version:        go1.21.11
Git commit:        5650f9b
Built:             Wed Jun  5 11:32:04 2024
OS/Arch: linux/amd64
Context:           default

Server: Docker Engine - Community
Engine:
Version:          26.1.4
API version:      1.45 (minimum version 1.24)
Go version:       go1.21.11
Git commit:       de5c9cf
Built:            Wed Jun  5 11:31:02 2024
OS/Arch: linux/amd64
Experimental:     false
containerd:
Version:          1.6.33
GitCommit: d2d58213f83a351ca8f528a95fbd145f5654e957
Run:
Version:          1.1.12
GitCommit:        v1.1.12-0-g51d5e94
docker-init:
Version:          0.19.0
GitCommit:        de40ad0

My docker version is already a newer version, why is the containerd version so low, and a warning message will be reported, prompting me to update to containerd v2.How can I do this?

2

Where did you get this error message? The latest containerd is 1.7.23. Containerd v2 is just a release candidate: Release containerd 2.0.0-rc.5 · containerd/containerd · GitHub

I have an even newer containerd version as my Docker version is newer too and I haven’t seen this error message anywhere.

update:

Okay, I found it in journal logs. I think you can safely ignore that message. You could use containerd without Docker but Docker will take care updating containerd or if anything will need to be done, you should find it in the documentation or release notes when the new version is used by Docker.