Why do podman commands throw the warning 'failed to decode the keys XXX' after upgrading to Podman 5.2 on Red Hat Enterprise Linux 9?

Solution Verified - Updated -

Issue

*Why do podman commands throw the warning 'failed to decode the keys XXX' after upgrading to Podman 5.2 on Red Hat Enterprise Linux 9?
*All podman command works but with a warning
Example

$ podman --version
WARN[0000] Failed to decode the keys ["storage.options.remap-uids" "storage.options.remap-gids" "storage.options.remap-user" "storage.options.remap-group" "storage.options.thinpool.xfs_nospace_max_retries" "storage.options.thinpool.xfs_nospace_max_retries" "storage.options.thinpool.xfs_nospace_max_retries" 
from "/home/testuser/.config/containers/storage.conf" 
podman version 5.2.2

Environment

  • Red Hat Enterprise Linux 9
  • podman updated from podman-4.9 to podman-5.2.X
  • Customized storage.conf for the rootless user

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content