jtolio
(JT Olio)
December 4, 2023, 3:31pm
1
Hello!
In every Kinoite release since 39.20231130.0 (the last working release, which I have pinned), up through 39.20231202.0, Toolbox fails to start for me.
All attempts to enter a toolbox fail with Error: failed to get the Podman version
.
Trying to get the podman version myself, I get:
Error: database libpod root directory (staticdir) "/home/jt/.local/share/containers/storage/libpod"
does not match our libpod root directory (staticdir)
"/var/home/jt/.local/share/containers/storage/libpod": database configuration mismatch
I observe that the only difference in these paths is the “/var” prefix. When I upgraded from Kinoite 38 to Kinoite 39, I noticed that bash would always say my PWD was “/var/home/jt” instead of “~” or something. I switched my PS1 and didn’t think more of it.
podman system reset
also fails with the above error. If I roll back to my last working Kinoite build, everything is fine.
Does anyone know what’s going on here?
Thanks!
castrojo
(Jorge Castro)
December 4, 2023, 3:33pm
2
This is the upstream issue:
opened 03:18PM - 01 Dec 23 UTC
closed 11:50AM - 03 Dec 23 UTC
kind/bug
regression
### Issue Description
Starting with version 4.8.0, I get the error below.
```
…
Error: database libpod root directory (staticdir) "/home/<user>/.local/share/containers/storage/libpod" does not match our libpod root directory (staticdir) "/var/home/<user>/.local/share/containers/storage/libpod": database configuration mismatch
```
I'm on Fedora Kinoite 39. No problems with version 4.7.2.
### Steps to reproduce the issue
Steps to reproduce the issue
1. Upgraded to 4.8.0 from 4.7.2.
2. Try to start a container
```
podman --log-level debug start postgres
```
### Describe the results you received
```
INFO[0000] podman filtering at log level debug
DEBU[0000] Called start.PersistentPreRunE(podman --log-level debug start postgres)
DEBU[0000] Using conmon: "/usr/bin/conmon"
INFO[0000] Using boltdb as database backend
DEBU[0000] Initializing boltdb state at /var/home/<user>/.local/share/containers/storage/libpod/bolt_state.db
DEBU[0000] Overriding graph root "/var/home/<user>/.local/share/containers/storage" with "/home/<user>/.local/share/containers/storage" from database
DEBU[0000] Using graph driver overlay
DEBU[0000] Using graph root /home/<user>/.local/share/containers/storage
DEBU[0000] Using run root /run/user/1000/containers
DEBU[0000] Using static dir /var/home/<user>/.local/share/containers/storage/libpod
DEBU[0000] Using tmp dir /run/user/1000/libpod/tmp
DEBU[0000] Using volume path /var/home/<user>/.local/share/containers/storage/volumes
DEBU[0000] Using transient store: false
Error: database libpod root directory (staticdir) "/home/<user>/.local/share/containers/storage/libpod" does not match our libpod root directory (staticdir) "/var/home/<user>/.local/share/containers/storage/libpod": database configuration mismatch
DEBU[0000] Shutting down engines
```
### Describe the results you expected
Container should start normally.
### podman info output
```yaml
Error: database libpod root directory (staticdir) "/home/<user>/.local/share/containers/storage/libpod" does not match our libpod root directory (staticdir) "/var/home/<user>/.local/share/containers/storage/libpod": database configuration mismatch
OS: Fedora Kinoite 39
Arch: x86_64
```
### Podman in a container
No
### Privileged Or Rootless
Rootless
### Upstream Latest Release
Yes
### Additional environment details
Running of bare metal.
### Additional information
None.
3 Likes
I can confirm this also happens on Kinoite beta
toolbox-0.0.99.4-5.fc40.x86_64
podman version 4.8.1
starfish
(Shek Yun Kwan)
August 23, 2024, 5:06pm
4
This is also happening on Kinoite 40 as of 40.20240823.0
toolbox 0.0.99.5
podman version 5.2.1
yuntaz
(Y.Z.)
August 24, 2024, 1:05am
5
I can confirm this issue, but it is slightly different this time.
Error: database volume path does not match our volume path: database configuration mismatch
Neither toolbox nor distrobox containers can be created.
A workaround for this issue is mentioned here:
opened 07:32AM - 06 Aug 24 UTC
closed 08:16AM - 07 Aug 24 UTC
kind/bug
### Issue Description
Starting with podman-5.2.0-1.el10, I get the following er… ror 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
3.
### 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
```yaml
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_
Simply run the following command:
mkdir -p ~/.local/share/containers/storage/volumes
1 Like