On Wed, Aug 24, 2016 at 2:52 AM, Christian Kniep <ckn...@gaikai.com> wrote: > Hey there, > > as for the /etc/hostname when sharing /etc/ as a volume… This ain’t a > problem as /etc/hostname is taken care of by the docker-engine (in previous > versions they used it to discover other hosts). >
Docker isn't the only container manager out there... Hopefully they only populate it if it already exists. But, yes, you can bind mount an individual file. In any case, my concern isn't so much with using /etc/hostname to SET the hostname. My concern is more with having other processes read /etc/hostname to determine the hostname. It just isn't the right way to do things. Maybe it should just be installed chmod 600 by default? :) -- Rich
