3 ms·
Looks like it should work with podman out of the box by setting the DOCKER_HOST environment variable to your podman socket. Or facing any compatibility issues?
by 3np 2y ago
Looks like it should work with podman out of the box by setting the DOCKER_HOST environment variable to your podman socket. Or facing any compatibility issues?
- yourapostasy 2y agoI imagine they'll run into some of the same issues lazydocker [1] did. It seems non-trivial for seamless, comprehensive compatibility. [1] https://github.com/jesseduffield/lazydocker/issues/4 https://github.com/jesseduffield/lazydocker/issues/4
- 3np 2y agoThe only issue I see mentioned when setting DOCKER_HOST to the podman socket is about log-integration not working for all containers, just like with docker? Ie no podman-specific issues. Some light usage here and no issues so far.
- donno 2y agoI gave it a spin with Podman on Windows and it did indeed work out of box. NO nee It listed containers, volumes and networks and started & stopped a container. The Terminal item expects the container to have bash, so would need some tweaking to use /bin/sh. I didn't need to set DOCKER_HOST, but I assume I have the Docker compatibility mode enabled.
- xlmnxp 2y agomodified the code to fallback to /bin/sh if /bin/bash not exists :)