-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
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
Unattended installation don't work. #5283
Comments
Looking at the code, pi-hole/automated install/basic-install.sh Lines 2570 to 2587 in d885e92
|
Hey great! Thanks for the help. I missed that part. Are the variables in the setupVars.conf the same as the env vars described in the docker container ? Now that I know what to google I can find other people finding similar questions. |
I think yes (without having checked all of them - some might be docker-specific) The ones the installer will set are those (+ pi-hole/automated install/basic-install.sh Lines 1834 to 1847 in d885e92
It never is. It's a lack of awareness or a lack of motivation. __
Please do so. All documentation changes are made at https://github.com/pi-hole/docs which are served at https://docs.pi-hole.net/ |
Versions
none yet.
Platform
Debian 11 on proxmox (or vagrant for development)
Expected behavior
The --unattended flag allows for automated install.
Actual behavior / bug
I still get dialog screens.
Steps to reproduce
Steps to reproduce the behavior:
Additional context
I added this debug out put to the script:
The results are:
It seems the flag is picked up but I still get the pretty blue dialog screens.
I saw that on line 2578 the variable
DEBIAN_FRONTEND
is set but never used again.The dialog screen is started right after on line 2587 without checking either
DEBIAN_FRONTEND
orrunUnattended
.I've tried to search in the git history for changes around this but I can't find anything significant as far as I can tell.
The text was updated successfully, but these errors were encountered: