Re:Codespaces but open-source, client-only, and unopinionated
by timmytokyo on Tuesday June 20, 2023 @02:52PM
(#36408748)
Tried it, but it doesn't seem to work with non-rootless podman as a replacement for docker.
[ Parent
| on HN ]
Re:Codespaces but open-source, client-only, and unopinionated
by gentele on Tuesday June 20, 2023 @02:55PM
(#36408777)
Thanks for trying it! Can you open an issue on GH about this or join us on slack, so we can dig deeper into making this work for non-root podman with your input?
Re:Codespaces but open-source, client-only, and unopinionated
by esafak on Tuesday June 20, 2023 @06:20PM
(#36411514)
Are you using podman for everything in production? I am still trying to understand when to use it.
Re:Codespaces but open-source, client-only, and unopinionated
by timmytokyo on Tuesday June 20, 2023 @06:54PM
(#36411872)
I don't have any experience using podman in production. I use it on my dev PC for work, where I have to run Windows. Previously I used Docker Desktop for Windows, but I got tired of dealing with its various annoyances. Podman has been a mostly seamless drop-in replacement. It doesn't support swarm, which I used to use with docker, but I've found a good solution using docker-compose instead.
Re:Codespaces but open-source, client-only, and unopinionated
by CoolCold on Wednesday June 21, 2023 @11:17AM
(#36419604)
Not using it yet, but basically there where you cannot control who runs what, like shared builders or server with personal beyond infra/itsec teams may have access and need to be able to run containers. As being in group Docker/having access to Docker socket effectively means having root access, Podman/rootless docker can be a savior.