We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The HOSTNAME env variable doesn't tend to bell
It should probably check against a regexp for the presence of a dot in the $HOSTNAME env variable:
/^[_a-z0-9-]+\.([_a-z0-9-]+\.?)+$/
would do the trick
Originally reported on Bytemark's Gitlab by @patch0 on 2017-04-21T19:29:30.820Z
The text was updated successfully, but these errors were encountered:
I think this was following testing inside docker containers, where HOSTNAME gets set weirdly, and really shouldn't be used.
Sorry, something went wrong.
it's causing similar problems with systemd containers i think
Is this bug meant to fix-up invalid $HOSTNAMEs by appending '.localdomain', or just complain early in the install process?
common: Fix postinst to append "localdomain" to unqualified hostnames
6970e92
Closes #57
telyn
No branches or pull requests
The HOSTNAME env variable doesn't tend to bell
It should probably check against a regexp for the presence of a dot in the $HOSTNAME env variable:
would do the trick
The text was updated successfully, but these errors were encountered: