-
Notifications
You must be signed in to change notification settings - Fork 34
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
Add Ubuntu 20.04 LTS #4
Comments
I actually tried to shoot you an email yesterday but your contact-me on your website wasn't working. I haven't had a chance to look at 20.04 yet but I'm really hoping we can get an unattended build together that puts /boot on /sda1 and everything else on LVM. |
Heh thanks for reminding me about that. Forgot they removed the old version of recaptcha I was using and haven't gotten around to updating it. If anything it looks like it will be even easier with the new config format since you can do things like matching on serial number or if it's an SSD. |
Hi again, I hate to ask, but I was hoping you might be able to help me better understand how to use the new build system to achieve something approaching parity with kickstart when it comes to static networking information. Our build method - and I'm guessing the build method for many more traditional places - is to use a single generalized kickstart file hosted on a web server (eg: ks=https://build.college.edu/ubuntu-1804-base.ks) coupled with kernel boot args for hostname/domain and static network information as we don't have PXE nor DHCP. After reading through your wiki pages, and the upstream docs, I'm still not quite grokking how to do the same for Ubuntu 20.04. Thanks a bunch for maintaining the "missing manual" to Ubuntu automated builds! |
Actually one of my TODO's is to just pull the 18.04 ks file. While poking around I saw that there were still some preseed files on boot media and while they recommend using the new system and the old kickstart method is deprecated it may still work. I have a hunch that would work though so if you really want to get up and going with deploying 20.04 (I usually try to have the auto install stuff working when they issue a |
So I've been looking in to this still. What's been eating my time away is how much stuff gets installed by default. Apparently this is just how it works now. Specifically all that stuff is coming from |
Include a more detailed user-data file to showcase some options that can be changed. Also explained the autoinstall process. Ref: gh-4
So just posted this little juicy tidbit to wiki page I figured I'd copy here:
So I may look at tweaking the kickstart config and just get that up, point people to get the 'legacy' image and it all works. Although I've still been meaning to tweak the sizes of default install. I always end up having to expand |
Thanks man! I'm going to try to make some time to also test this out for work. |
Since last update there has been a lot more information available online. Including Ubuntu's own documentation is much better now. Prepping for 22.04 I may give it another go to see if I can install a minimal vm without snap or any other non-essential things. I've done inplace upgrades of a couple servers. One autoinstalled snapd and another didn't. But I removed it from the one that did and it still runs fine. Perhaps the wwhole grub issue I was having before is fixed now? Just wanted to update this with some links as many people have gotten this to work now albeit the resultant images are larger than I'd like. |
Ubuntu 20.04 LTS has been released. Some observations thus far:
alternate installer
. Only option is the live cd, even for netbootLikely this is going to involve scrapping the use of
kickstart
format files and using the newer format. Which doesn't look too difficult. So I'm thinkingThe text was updated successfully, but these errors were encountered: