Error: database volume path does not match our volume path: database configuration mismatch

[shi2wei3]

Issue Description

Starting with podman-5.2.0-1.el10, I get the following error in centos-bootc(rpm-ostree) rootless mode
home -> var/home
$HOME=/home/admin

Error: database volume path "/home/admin/.local/share/containers/storage/volumes" does not match our volume path "/var/home/admin/.local/share/containers/storage/volumes": database configurat
ion mismatch

This bug starts with CentOS-Stream-10-20240805.0 with podman-5.2.0-1.el10
No exists on CentOS-Stream-10-20240802.0 with podman-5.1.2-2.el10

Steps to reproduce the issue

Steps to reproduce the issue

1. boot centos-bootc:stream10 with podman-5.2.0-1.el10
2. run podman system info in rootless

Describe the results you received

Error: database volume path "/home/admin/.local/share/containers/storage/volumes" does not match our volume path "/var/home/admin/.local/share/containers/storage/volumes": database configurat
ion mismatch

Describe the results you expected

podman system info

podman info output

Error: database volume path "/home/admin/.local/share/containers/storage/volumes" does not match our volume path "/var/home/admin/.local/share/containers/storage/volumes": database configurat
ion mismatch

### Podman in a container

No

### Privileged Or Rootless

Rootless

### Upstream Latest Release

Yes

### Additional environment details

centos-bootc:stream10 with podman-5.2.0-1.el10 deployed on a KVM guest

### Additional information

_No response_

[Luap99]

@mheon PTAL

[mheon]

Ah, I see now. Volume path doesn't exist, so evalSymlinksIfExists doesn't have a symlink to evaluate and so just cleans the path, leading to a /var/home vs /home mismatch on OSTree.

Best solution probably just to create the path as part of Podman init.

As a workaround, you can mkdir /home/admin/.local/share/containers/storage/volumes and, now that the directory exists, the symlink we be evaluated correctly and things should go back to working.

[j-dominguez9]

Also having this issue on fedora silverblue after rpm-ostree update

[mheon]

Uh-oh, we didn’t cherry pick this into 5.2.1. Will probably require a second patch release. We want this in the next stable RHEL release

…

On Fri, Aug 16, 2024 at 09:42 Joaquin Dominguez ***@***.***> wrote: Also having this issue on fedora silverblue after rpm-ostree update — Reply to this email directly, view it on GitHub <#23515 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB3AOCHXALEOBT7SG2DMKJTZRX6VXAVCNFSM6AAAAABMBXBSBCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJTGUZTMNZXG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[rmb938]

Having same problem as @j-dominguez9 on Fedora Kionite. Fixed it by running what was mentioned above mkdir /home/${USER}/.local/share/containers/storage/volumes