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