Implement the good ideas in http://phusion.github.io/baseimage-docker/
A permanent container should also have syslog, cron, and ssh. These are optional but for an urbit host, ssh is probably desirable. Also having a less janky init would be good -- it's not clear if the reasons runit were chosen are still good reasons when the container is meant to host a single-process Urbit pier.
A fun experiment would also be starting up multiple piers (destroyer? cruiser, carrier) on boot via runit, and automatically starting :chat only if it's not already running, setting a wide enough window size to prevent Arvo wrapping the lines, and hooking the output up to syslog where timestamps can be magically placed on the chat log; exposing an interface to get yacht tickets and let ssh users consume them safely within the urbinit yacht startup suite, etc.
So this is at least three separate branches, not really all for one pull request...
Can we make a good recipe for an "anonymous chat logging" container that joins chat automatically and adds local timestamps to a private room log
What should vere look like when started here by an init system / how to we use daemon mode correctly to make a good pier host, or is it completely appropriate for this case
How to distribute yacht tickets or any other kind of tickets in a fairly automated way (say, to subscribing / paying customers, who should also get console access and may even be in a position to sink their own ships from the batz shell)
Implement the good ideas in http://phusion.github.io/baseimage-docker/ A permanent container should also have syslog, cron, and ssh. These are optional but for an urbit host, ssh is probably desirable. Also having a less janky init would be good -- it's not clear if the reasons runit were chosen are still good reasons when the container is meant to host a single-process Urbit pier.
A fun experiment would also be starting up multiple piers (destroyer? cruiser, carrier) on boot via runit, and automatically starting :chat only if it's not already running, setting a wide enough window size to prevent Arvo wrapping the lines, and hooking the output up to syslog where timestamps can be magically placed on the chat log; exposing an interface to get yacht tickets and let ssh users consume them safely within the urbinit yacht startup suite, etc.