Re:Linux 3.8 introduced unprivileged user namespaces [pdf]
by ghevshoo on Wednesday December 18, 2019 @01:47PM
(#21827902)
Maybe podman “just works” on Linux but it still has some work to be done before the same could be said for macOS.
E.g. https://github.com/containers/libpod/issues/4039#issuecommen...
Re:Linux 3.8 introduced unprivileged user namespaces [pdf]
by jchw on Wednesday December 18, 2019 @04:48PM
(#21829823)
Ultimately Docker on macOS is just Docker on Linux in a VM over TCP (and it’s not open source.)
To be less nebulous: regarding the problem of being “rootless,” macOS support is neither here nor there. As far as I can tell it doesn’t really matter since the containers are already in a VM anyways.
Re:Linux 3.8 introduced unprivileged user namespaces [pdf]
by aorth on Wednesday December 18, 2019 @12:56PM
(#21827408)
> You can `alias podman=docker` and it will just work.
Yes, and it's super awesome. Unless you need docker-compose!
Re:Linux 3.8 introduced unprivileged user namespaces [pdf]
by thinkmassive on Wednesday December 18, 2019 @02:07PM
(#21828121)
Podman supports pods, hence the name. It follows the k8s approach, and it’s nowhere close to a drop-in replacement for docker-compose, but managing multiple related containers is supported as a core feature.
https://developers.redhat.com/blog/2019/01/15/podman-managin...
Re:Linux 3.8 introduced unprivileged user namespaces [pdf]
by thenewnewguy on Wednesday December 18, 2019 @03:39PM
(#21829171)
> Unless you need docker-compose!
There's a solution for that :) (Note: still somewhat beta quality)
For an almost drop-in daemonless, rootless docker replacement for this use case, see podman (https://podman.io/). You can `alias podman=docker` and it will just work.
You do need a bit of configuration, specifically you need to create `/etc/subuid` and `/etc/subgid` if they don't exist and add subordinate UIDs/GIDs which will be used to map the containers users and groups. E.g.