BTW: I'm considering writing my own "supervisord"-like in go (to make it single binary)
which unlike runit, s6 and others does not intend to be full init system (no ttys, no logs, no crons) just like supervisord, it just process supervisor that allow you to run multiprocess container. I'm considering an almost compatible ini syntax to systemd (so it could be called go-systemd, or yet another fake systemd) why not just supervisord, because we are considering python-less micro base image for apps that does not need python specially go binary containers (ex. busybox, etcd, kube*, .. ) but I'm not sure if this is even a good idea or not On Thu, Jul 14, 2016 at 12:02 AM, Muayyad AlSadi <als...@gmail.com> wrote: > Try fake runtime which provides systemd (fake one indeed). > > On Wed, Jul 13, 2016, 11:55 PM Colin Walters <walt...@verbum.org> wrote: > >> >> >> On Mon, Jun 20, 2016, at 01:57 PM, Micah Abbott wrote: >> > On 06/20/2016 09:38 AM, Joe Brockmeier wrote: >> > > Have we published any comparisons of an Alpine image "fully loaded" >> > > (e.g., with the actual tools) vs. Fedora, etc.? AIUI, when you >> actually >> > > install things like Apache httpd, or whatnot the comparison looks much >> > > closer. >> > >> > I hacked up some quick Dockerfiles for this particular example (httpd) >> > and the end result is that alpine was still smaller - 8.652 MB vs. >> 232.8 MB >> >> The largest chunk of this is that the httpd RPM pulls in systemd, and >> that's >> going to be true presently for a lot of our RPMs. So that's a whole >> subthread to this. >> >> It'd be possible to teach micro-yuminst to just ignore requirements >> on specific packages like systemd, while still allowing anyone who >> explicitly >> wants them to pull them in. >> >>
