1

My syslog has these warnings:

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

Very useful. So, as instructed, I do:

sudo containerd config migrate

I get this response:

No help topic for 'migrate'

This is really unhelpful.

I have never altered my containerd configuration, so I am surprised that when containerd upgraded, the configuration wasn't also automatically upgraded, as happens with all other packages.

My OS is XUbuntu 24.04.3 LTS and my machine was freshly installed about 6 months ago, so I am a bit surprised that this is happening, that the LTS transistioned from one version of containerd to another. LTS releases are supposed to be more stable.

I have searched the internet and while there are lots of articles about the transition, none of them give clear concise instructions on how to migrate my config. I cannot even figure out where the config file lives.

Can anyone provide clear, concise, instructions on how to migrate a default containerd configuration from version 1 to version 2?

Improve this question
4
  • Are you running containerd v2.0? containerd --version Commented Oct 30 at 18:56
  • containerd containerd.io v1.7.28 b98a3aace656320842a23f4a392a33f46af97866 Commented Oct 31 at 11:34
  • Good question. No, so why is it warning me of this? Commented Oct 31 at 11:35
  • It's a warning, not an error. Most all of us will ignore it until something breaks. Commented Oct 31 at 13:18

0

Reset to default

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.