Comment 2 for bug 1906970
Revision history for this message
| Klaus Frank (agowa338) wrote Re: dpkg hook hostname error | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
4d1350f
(Get the code!)
This is the default name of the docker container. That's why I reported it here. For me it is a problem with the install script. It shouldn't fail to install within a default docker container.
regarding b) how do I make docker select that automatically? I wasn't able to find any way to install postfix silently except by the commands and environment variables listed above.
{quote}
Fqdn's are a defined standard, and if your name would be like one it should work.
Never the less we try to catch and handle some common issues.
It might be worth for your to look at your hostname in general (report your full name here please) and the code that the install runs you can find in /var/lib/
If therein is an issue that could be improved to support your kind of hostname better that might be worth a talk.
{quote}
I already provided that. The hostname is just "cc1a572af0dc" without domain. It is set by docker. I don't know how I would influence that at build time.
I also provided where in the post install script it fails and why. It fails within that function when you try to work around the missing domain part in the fqdn by appending the "search" part from /etc/resolv.conf. That part generates an invalid host name and writes that into the postfix configuration and than tries to start postfix using it which makes dpkg fail.
THe resolv.conf is also written by docker and therefore also outside of my control.
And here is an asciinema recording, maybe that helps to show what the problem is:
* https:/