Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: database storage temporary directory (runroot) "" does not match our storage temporary directory (runroot) "/var/tmp/podman_test2131378507/runroot": database configuration mismatch #21270

Closed
edsantiago opened this issue Jan 16, 2024 · 4 comments
Labels
flakes Flakes from Continuous Integration kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. stale-issue

Comments

@edsantiago
Copy link
Member

Seen just now in f38 root, in #17831 which has no flake retries:

Podman run with --sig-proxy
  [It] signals are not forwarded to container with sig-proxy false
 .....
  # podman [options] run --name test2 --sig-proxy=false quay.io/libpod/systemd-image:20230531 bash -c trap "echo Received" SIGFPE; while :; do sleep 0.25; done
  # podman [options] ps -q
  Error: database storage temporary directory (runroot) "" does not match our storage temporary directory (runroot) "/var/tmp/podman_test2131378507/runroot": database configuration mismatch

My cirrus-flake-grep shows no other instances of this. Even though this is a one-off, I'm filing anyway because I just really don't like it.

@edsantiago edsantiago added flakes Flakes from Continuous Integration kind/bug Categorizes issue or PR as related to a bug. labels Jan 16, 2024
@mheon
Copy link
Member

mheon commented Jan 16, 2024

F38 root boltdb? We have a lot of special handling around putting the empty string in DB paths in Bolt, and none in SQLite, so that's kind of surprising.

Copy link

A friendly reminder that this issue had no activity for 30 days.

@Luap99
Copy link
Member

Luap99 commented Apr 4, 2024

@edsantiago Still seeing this?

@edsantiago
Copy link
Member Author

Nope, only that one time. Let's sweep it under the rug.

@edsantiago edsantiago closed this as not planned Won't fix, can't repro, duplicate, stale Apr 4, 2024
@stale-locking-app stale-locking-app bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Jul 4, 2024
@stale-locking-app stale-locking-app bot locked as resolved and limited conversation to collaborators Jul 4, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
flakes Flakes from Continuous Integration kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. stale-issue
Projects
None yet
Development

No branches or pull requests

3 participants