INN and docker default hostnames

[Julien ÉLIE]

Hi Richard,

> Firstly the use case is not 'running INN without an FQDN'. The use case 
> is installation only. The random hostnames only exist during 
> installation; by the time the news server is exchanging articles, INN 
> has a normal pathhost.

How can INN determine that its installation is not finished?


> Secondly the chance that the Docker random hostnames are globally unique 
> is very very high. They are random 96-bit strings and only exist for a 
> short time.

Under the use case of installation only, one possibility is Docker but 
there are others.  We cannot be sure that there is a random generated 
hostname.  It may be a hard-coded "buildkitsandbox" hostname without any 
randomness, or any other string.


> In short I think the concerns about relaxing INN's check are not really 
> well-founded.

We could also keep the check, writing the warning in the logs but not 
making it fatal.  Instead of a warning, it could be a (non-fatal) error 
so that the news admin sees it (the log file is sometimes separate).

-- 
Julien ÉLIE

« Vita breuis, ars longa, occasio praeceps, experimentum pericolosum,
   iudicium difficile. » (Hippocrate)