INN and docker default hostnames

[Richard Kettlewell]

On 04/04/2020 18:41, Russ Allbery wrote:
> Richard Kettlewell <rjk at terraraq.uk> writes:
> 
>> However, INN hates it, and refuses to even install:
> 
> INN refuses to run with a single component hostname because the chances
> are low that it's globally unique, and historically INN considers it
> unsafe to run without an FQDN to put in the Path.  This is an old, old
> check, predating containers and Docker and all of that world.

Of course it isn't actually going to run with a dotless pathhost; it 
will be properly configured subsequent to installation.

> I do think it's at least mildly dubious to run INN without an FQDN to put
> into the Path header.  It's kind of obnoxious for innconfval to fail
> (that's because there's only one inn.conf parser and it behaves the same
> way for everything).

Yes.

> The quick fix would probably be to find a way to preseed the domain name
> so that the package installation succeeds (which may not be supported by
> the Debian packaging currently).  I'm a little dubious about relaxing this
> check in general, since putting unqualified hostnames in the Path header
> and using them for loop checking sounds likely to cause weird problems.

I see where you're coming from, but dotless pathhost isn't actually the 
goal here. It's not even going to exchange any articles during the 
'docker build' step, that only happens much later.

If Debian had a way to preseed INN configuration then I'd use it, but it 
doesn't, so here we are...

ttfn/rjk