autoinstalls are not like this: by default, if there is any autoinstall config at all, the installer takes the default for any unanswered question (and fails if there is no default).
when the answer to a question is not present in a preseed, d-i stops and asks the user for input.the format is completely different (cloud-init config, usually yaml, vs debconf-set-selections format).Preseeds are the way to automate an installer based on debian-installer (aka d-i).Īutoinstalls for the new server installer differ from preseeds in the following main ways: Here's the important bit: Differences from debian-installer preseeding The SERVER installer ( subiquity) is no longer based upon d-i, and you use a subsection of the existing cloud-config file.The DESKTOP installer ( ubiquity) is based upon debian-installer, and you use a preseed file.There's a whole section of on this topic. Has anyone solved this issue? Is there a way to force the usage of a certain preseed file? Thanks in advance iso file, but I am curious why this approach is not working? cfg files and tried to solve the problem, which in my case didnt change anything. I couldnt find any information on this, except that some people made a patch fix on the. Seems like the installation ignores the input from the preseeds. However, when I wanted to do the same with the Ubuntu Server distributions (18.04 and 20.04), the installation process started prompting for user input such as language, username, pw etc, even all the information was provided in the preseeds.cfg.
So I made the some scripts for the Desktop Ubuntu distributions 18.04 and 20.04 and everything worked fine.Įverything worked perfectly, u just run it and it installs from start to end without any prompting. The main goal is to install a VirtualMachine without any prompting. I was making today scripts for automated VirtualBox installation via VBoxManage.
0 kommentar(er)
