Docker 19.03: Rootless Mode (Experimental)
1–10 of 45 posts
Re: Docker 19.03: Rootless Mode (Experimental)
#2Or we could just ditch Docker for one of the alternatives, like Podman that doesn't need root, nor a daemon.
Re: Docker 19.03: Rootless Mode (Experimental)
#3Or we could just ditch Docker for one of the alternatives, like Podman that doesn't need root, nor a daemon.
Comparing the shortcomings of rootless podman (https://github.com/containers/libpod/blob/master/rootless.md) and rootless docker, they seem almost the same. So this argument may not count, the daemon argument however applies.
Re: Docker 19.03: Rootless Mode (Experimental)
#4Or we could just ditch Docker for one of the alternatives, like Podman that doesn't need root, nor a daemon.
I don't like their idea of what a docker-compose replacement should be. And reading issues and limitations about podman pod commands is very discouraging. I would love to hear what others are using and their experiences though. I avoid anything Kubernetes because of a personal bias.
Re: Docker 19.03: Rootless Mode (Experimental)
#5Or we could just ditch Docker for one of the alternatives, like Podman that doesn't need root, nor a daemon.
Yep. I only half care about rootless. I definitely care about the daemon.
It sucks.
It flies in the face of traditional Linux process management where child processes are child processes.
(Unless you want an init system, where you need a daemon. But docker is a sucky init system.)
Docker breaks even the most basic things.
$ time docker run some heavy computation
Re: Docker 19.03: Rootless Mode (Experimental)
#6Or we could just ditch Docker for one of the alternatives, like Podman that doesn't need root, nor a daemon.
I don't like their idea of what a docker-compose replacement should be. And reading issues and limitations about podman pod commands is very discouraging. I would love to hear what others are using and their experiences though. I avoid anything Kubernetes because of a personal bias.
Would you be willing to elaborate on the reason why you avoid kubernetes?
Re: Docker 19.03: Rootless Mode (Experimental)
#7Earlier quoted context omitted.
I don't like their idea of what a docker-compose replacement should be. And reading issues and limitations about podman pod commands is very discouraging. I would love to hear what others are using and their experiences though. I avoid anything Kubernetes because of a personal bias.
Would you be willing to elaborate on the reason why you avoid kubernetes?
Like I said it's a personal bias, mainly about Google. The only time I had to use it was with RH's cloud and if it wasn't for their good documentation I would have dropped the client. Everytime I looked under the hood it reminded why I hate being a developer around 35% of the time.
Re: Docker 19.03: Rootless Mode (Experimental)
#8Or we could just ditch Docker for one of the alternatives, like Podman that doesn't need root, nor a daemon.
Yep. I only half care about rootless. I definitely care about the daemon. It sucks. It flies in the face of traditional Linux process management where child processes are child processes . (Unless you want an init system, where you need a daemon. But docker is a sucky init system.) Docker breaks even the most basic things. $ time docker run some heavy computation Oh wait, that doesn't work.
For the trivial case a child process would work. But ultimately docker does try to be closer to an init system or maybe screen since you can detach/attach to processes. Since reparenting to arbitrary processes is not possible in linux it's also not possible to retain the parent-child relationship for spawned containers.
If you want the fork-exec model then docker is indeed the wrong tool for the job.
Re: Docker 19.03: Rootless Mode (Experimental)
#9Earlier quoted context omitted.
Yep. I only half care about rootless. I definitely care about the daemon. It sucks. It flies in the face of traditional Linux process management where child processes are child processes . (Unless you want an init system, where you need a daemon. But docker is a sucky init system.) Docker breaks even the most basic things. $ time docker run some heavy computation Oh wait, that doesn't work.
For the trivial case a child process would work. But ultimately docker does try to be closer to an init system or maybe screen since you can detach/attach to processes. Since reparenting to arbitrary processes is not possible in linux it's also not possible to retain the parent-child relationship for spawned containers. If you want the fork-exec model then docker is indeed the wrong tool for the job.
The thing is, I don't even really like Docker as an init daemon. I have my gripes about Systemd but I see no downsides to not having a long-running daemon for a container engine. Really, whether you need root or not isn't even the most important issue; you can do sudo or suid or whatever with any container engine; Docker just has it be an implicit, unintuitive behavior.
I used to use systemd+rkt for simple container setups when I didn't need all of Kubernetes. Never noticed any downsides versus using Docker, but on the flip side, I had far fewer issues with my containers not properly starting at boot.
Re: Docker 19.03: Rootless Mode (Experimental)
#10Docker has supported namespaces for a while now so that even if the user in the container is root it could be a subordinate id on the host with no administrative authority. What is new though?