Yeah that&#x27;s cool, but my main point is that images which make use of the stable debian package system and are actively maintained are a better approach than an image that makes use of more obscure technology that could be abandoned, or worse, maintaining your own container infrastructure.<p>&gt; No well, written software won&#x27;t spawn zombie-processes - sorry.<p>And yet it happens.<p>&gt; The ssh server... Containers are no vm&#x27;s, if you have to log in on a container running in production - you&#x27;re doing something wrong<p>The SSH server is incredibly useful for diagnosing problems in production, so I for one applaud it (although it&#x27;s not really necessary anymore with docker exec).<p>&gt; Cron - again - same thing: run in a separate container and give access to the exact things your cronjob needs.<p>Or just run it in-container to keep your service clusters together.<p>&gt; That is for me the essential thing about containers: separate everything.<p>It&#x27;s a question of degree. Where you draw the line is almost always a personal, aesthetic choice.