Minikube fails to detect Podman container IP when BoltDB deprecation warning is emitted (Fedora 42, Podman 5.7.0, boltdb)

[alekonko]

Cosa è successo?

log.txt

Minikube fails to start when using the Podman driver if Podman emits the BoltDB deprecation warning.
The warning interferes with Minikube’s parsing of podman inspect output, causing Minikube to incorrectly fall back to the lo interface (127.0.0.1) and fail with:

unable to select an IP from lo network interface

This appears to be a parsing/robustness issue in Minikube when handling non-empty stderr output from Podman.

---

Environment

• OS: Fedora 42
• Minikube: v1.36.0
• Driver: podman
• Podman: 5.7.0
• Podman database backend: BoltDB (legacy)
• Runtime: rootful (via sudo)

---

Steps to Reproduce

1. Install Fedora 42 with Podman 5.7.0 still configured to use BoltDB.
2. Ensure the BoltDB deprecation warning is not suppressed.
3. Run:

   minikube start --driver=podman

   or

   minikube -p minikube-new start --driver=podman

Observed Behavior

• Minikube startup fails with:

  unable to select an IP from lo network interface
  

• Debug logs (--alsologtostderr --v=8) show Minikube retrieving network data using:

podman container inspect -f {{.NetworkSettings.IPAddress}} minikube
podman container inspect -f "{{range .NetworkSettings.Networks}}{{.IPAddress}},{{.GlobalIPv6Address}}{{end}}" minikube

• Podman emits the following warning on stderr:

WARN[0000] The deprecated BoltDB database driver is in use. This driver will be removed in the upcoming Podman 6.0 release...

Expected Behavior

Minikube should correctly detect the Podman container IP regardless of non-fatal warnings printed to stderr by Podman.

Workarounds

Any of the following restore correct behavior:

1. Suppress the BoltDB warning for sudo commands and Wait for safe db migration

echo "SUPPRESS_BOLTDB_WARNING=true" >> /etc/environment

2. DISRUPTIVE WAY migrate BoltDB, but lost your current minikube profile

Allegare il file di log

log.txt

Sistema operativo

Redhat/Fedora

Driver

Podman

[afbjorklund]

The code is only parsing stdout, so any output on stderr should not affect the outcome. Probably something else changed?

podman container inspect -f {{.NetworkSettings.IPAddress}} minikube

EDIT: It seems that the docker parsing is using stderr, so maybe that is the problem (not compatible with Docker)

podman container inspect -f "{{range .NetworkSettings.Networks}}{{.IPAddress}},{{.GlobalIPv6Address}}{{end}}" minikube

[afbjorklund]

This is the recommended workaround, for now:

export "SUPPRESS_BOLTDB_WARNING=true"

Many users are still running Podman 4.9 or 5.4

Mostly because there are no newer for Ubuntu