#INSTALL HAPROXY ON ALPINE HOW TO#
I however prefer isolating every single process and explicitly telling it how to communicate with other processes. But sure, you could treat containers as a special VM only for one service - nobody is going to stop you.
That is for me the essential thing about containers: separate everything. Containers are no vm's, if you have to log in on a container running in production - you're doing something wrong - unless that container's only job is running SSH (which can be useful for example for Jenkins build slaves).Ĭron - again - same thing: run in a separate container and give access to the exact things your cronjob needs. Logrotate - sure, useful - but if you care about logs and aren't sending them to your logger daemon or /dev/null, you probably want to store them externally - in a volume or mounted host directory - and have a separate container taking care of that. Guess mounting /dev/log into a container is too complex if you care about this?
Reaping dead child processes is something pretty basic if you're using "fork".Īnd then - a logger daemon. No well, written software won't spawn zombie-processes - sorry. The existence of the them has been defended by 'fixing' many so-called problems that are actually no problem at all - or at least shouldn't be a problem if you know what the hell you're doing. Sorry - but the phusion images are unnecessarily bloated.