4 ms·
Docker itself as PID 1 is… creative. Good things they've thought through: - boots fast, does almost the absolute minimum it needs to get up and running - sup
by jdub 12y ago
Docker itself as PID 1 is… creative.
Good things they've thought through:
- boots fast, does almost the absolute minimum it needs to get up and running
- supporting user data and at least minimal config via cloud-init
- properly minimal: you have to use a Debian image to set up persistent storage with mkfs.ext4! (edit: when using the ISO version, which is not the primary use case)
- but helpfully familiar: you can install distro flavoured "console" experiences with more than just busybox
- it's almost a better Boot2Docker than Boot2Docker! (a little bit of love for VirtualBox / VMware shared storage wouldn't go astray)
- riobard 12y agoI'm not sure… running a 7MB binary with tons of functionality as PID 1 sounds like a really bad idea. Possibly even worse than the usual complaints against systemd (which has at least process isolations for its various features).
- jdub 12y agoWho has a 7MB binary with tons of functionality as PID 1? That doesn't describe RancherOS or systemd. (Edit: Oh, you mean Docker itself as PID 1 on RancherOS. Yes, that's true. Certainly hairier than systemd. I haven't really dug into how much they limit what system-docker can do.)
- jdub 12y agoInteresting data point: - /usr/bin/systemd-docker = 8.4M - /usr/bin/docker = 14.3M
- NeutronBoy 12y agoFrom a security perspective, not really, the alternative is run Docker as root. Perhaps it is from a system stability perspective though?