see containers/storage@137ba2c

I guess the default storage.conf in the containers-common rpm has to get updated to remove the section.

I would humbly suggest that a better solution would be to fix storage.conf first, then wait for it to distribute everywhere that podman can possibly run, and then settle, and then remove thinpool from podman.

FYI: thinpool was never part of podman (well not for years)

Sorry, I misspoke due to haste.

As a podman user, I am not likely to know or care what thinpool is. If I upgrade podman, maybe on some distro that is not 100% careful about bumping c-common, I will see the above warning and I will waste time worrying about it. Multiply by hundreds or thousands of users.

I would like to encourage our team to take steps such that no user ever sees this warning. (Possible exception for someone with a custom /etc file, but even then it should say "that block of settings has not worked for a long time, please remove everything from [storage.options.thinpool] to the next bracketed section".)

Rawhide should have it removed now. We could tone down containers/storage verifying its storage.conf file, but that could lead to people adding bad settings and not knowing they have typos in storage.conf files.