Bug Description
I ran into an install issue on Fedora that seems like a packaging problem. ToolHive docs say Podman is supported on Linux, but the RPM appears to hard-require Docker.
docker >= 20.10
On Fedora, that makes dnf try to install moby-engine, which conflicts with podman-docker.
Steps to Reproduce
Just use dnf to install on Fedora?
sudo dnf install https://releases.toolhive.dev/stable/0.32.0/linux/x64/ToolHive-0.32.0-1.x86_64.rpm
Expected Behavior
- RPM should install cleanly on a supported Podman setup
- or at least not force moby-engine when Podman is the intended runtime
Actual Behavior
- RPM install fails because of the hard Docker dependency
Failed to resolve the transaction:
Problem: problem with installed package
- installed package podman-docker-5:5.8.2-1.fc43.noarch conflicts with docker provided by moby-engine-28.4.0-1.fc43.x86_64 from fedora
- installed package podman-docker-5:5.8.2-1.fc43.noarch conflicts with moby-engine provided by moby-engine-28.4.0-1.fc43.x86_64 from fedora
- package ToolHive-0.32.0-1.x86_64 from @commandline requires docker >= 20.10, but none of the providers can be installed
- conflicting requests
I also checked the RPM metadata directly and it does indeed require:
docker >= 20.10
Priority
Low
Environment
- Fedora 43
- KDE Plasma / Wayland
- Podman installed
- podman-docker installed
- no Docker / moby engine installed
Additional Context
Workaround:
- install the Linux tarball instead of the RPM
- enable the user Podman socket
- launch ToolHive with the Podman socket exposed via DOCKER_HOST
Bug Description
I ran into an install issue on Fedora that seems like a packaging problem. ToolHive docs say Podman is supported on Linux, but the RPM appears to hard-require Docker.
docker >= 20.10
On Fedora, that makes dnf try to install moby-engine, which conflicts with podman-docker.
Steps to Reproduce
Just use dnf to install on Fedora?
sudo dnf install https://releases.toolhive.dev/stable/0.32.0/linux/x64/ToolHive-0.32.0-1.x86_64.rpm
Expected Behavior
Actual Behavior
Failed to resolve the transaction:
Problem: problem with installed package
I also checked the RPM metadata directly and it does indeed require:
docker >= 20.10
Priority
Low
Environment
Additional Context
Workaround: