⚠️ Homebrew support is being deprecated. Solo will stop publishing updates to Homebrew after August 31, 2026. Install via npm install -g @hiero-ledger/solo@latest instead. See System Readiness for full install instructions.

SOLO-5077

PodmanRuntimeConfigurationFailedSoloError — System

PodmanRuntimeConfigurationFailedSoloError

CodeSOLO-5077
CategorySystem
OwnershipInfrastructure
RetryableNo

Description

Thrown when the container runtime stack behind the Homebrew-installed podman on Linux cannot be configured or fails its post-configuration probe — for example the crun or conmon binary is missing from the Homebrew prefix, a network helper download failed, or podman rejects the generated configuration. Without this configuration podman would fall back to the host’s system container stack, which may be too old for it.

Troubleshooting Steps

  1. Check solo logs: tail -n 100 ~/.solo/logs/solo.log
  2. Verify the Homebrew podman installation: brew doctor && podman info
  3. Inspect the generated configuration files under ~/.solo/config (containers.conf, registries.conf)
  4. Reinstall the Homebrew podman stack if binaries are missing: brew reinstall podman