On Tue, 07.10.14 14:14, Michal Sekletar (msekl...@redhat.com) wrote: > > Hence, if a container manager mounts everything properly, then mount_setup() > > should be a NOP anyway... > > In theory yes, but in fact not having /run mounted as tmpfs is default in the > docker > container. I have no strong opinion on whether this is sensible or not, > however > I think that systemd can be made more resilient and handle such > cases.
Sorry, but no. /run should be pre-mounted, and if it isn't we need the rights to mount it. We will not boot up a system without /run. That's part of the API for programs, and we will not avoid it. Please ask Docker to premount /run. All distros need /run anyway these days, Debian does, Ubuntu does, Fedora does. > Now systemd will try to mount /run on tmpfs, such attempt will fail because of > missing capability and then systemd will just hang. Well, just sticking the head in the sand won't help. If we don't have /run mounted, then things will break later on. We cannot ignore that. Sorry, Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel