You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Background: distrobox added Lilipod support in 2023 (commit 2201de4) and shipped it in 1.6.0. Issue #1710 showed flag incompatibilities (lilipod rm --volumes) before the rewrite.
Current main only has docker, podman, and podman-launcher providers. buildContainerManager does not recognize lilipod; autodetect only probes those three. The docs (docs/compatibility.md, docs/posts/install_lilipod_static.md, and a comment in pkg/containermanager/providers/podman.go) still mention lilipod.
Questions:
Was the Go provider intentionally dropped, or just not ported yet?
Is a Lilipod provider on the roadmap? If yes, when?
Can the docs be updated to match the code (or the code to match the docs)?
If lilipod comes back, would you accept a PR that ports the existing shell branches?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Background: distrobox added Lilipod support in 2023 (commit
2201de4) and shipped it in 1.6.0. Issue #1710 showed flag incompatibilities (lilipod rm --volumes) before the rewrite.Current
mainonly hasdocker,podman, andpodman-launcherproviders.buildContainerManagerdoes not recognizelilipod;autodetectonly probes those three. The docs (docs/compatibility.md,docs/posts/install_lilipod_static.md, and a comment inpkg/containermanager/providers/podman.go) still mention lilipod.Questions:
Links:
All reactions