Packer template for Ubuntu2204

geerlingguy / packer-boxes

Jeff Geerling's Packer build configurations for Vagrant boxes.

https://app.vagrantup.com/geerlingguy

MIT License

651 stars 304 forks source link

Packer template for Ubuntu2204 #95

Open maroskukan opened 2 years ago

maroskukan commented 2 years ago

Hey Jeff, this should address #93 . I was working on this a little while. It should be aligned with the rest of your builds, uses json and same provisioning scripts as your other boxes.

Some differences include:

user-data definition for cloud init as oppose to kickstart file for d-i
nfs_udp: false added to synced folder as described in this issue

Some technical details: Builder on Ubuntu 20.04, VirtualBox 6.1.34 Tested on Ubuntu 20.04 and MacOS Sierra.

Hope you find these useful.

Fixes: #93

geerlingguy commented 1 year ago

Thank you! I'll grab this and test as soon as I get a chance, and hopefully be able to push a build up to geerlingguy/ubuntu2204!

maroskukan commented 1 year ago

No worries @geerlingguy I think in the meantime there was a new minor release of the source iso. I can update this PR or you could change that afterwards. Let me know. This build should still work though.

stevenscg commented 1 year ago

@maroskukan I'm trying to replicate some of your work here with the 22.04.1 live server image. I keep getting thrown into the interactive install process starting with the language selection. Did you encounter anything similar?

maroskukan commented 1 year ago

Hi @stevenscg , yes. It could be caused by number of things:

Firmware selection, process differs for each of them

BIOS (I believe this is what you are using now)
EFI

Other issues that may cause you ending up in interactive shell could be influenced in the template by:

boot timeout
boot commands (e.g. line breaks, escapes etc)

It could be also caused if user-data is not reachable for some reason during installation.

What I would suggest is to perform the installation using user-data file hosted from simple web server (e.g. python -m http-server). And then appending the required arguments to boot command. You can then see whether it fetched the file and failed.

This multi-provider blueprint could help.

stevenscg commented 1 year ago

@maroskukan Thanks. I'll see if I can figure out and test with the standalone method. FWIW, I tried this branch with only the following URL changed and still get thrown into the interactive mode: https://old-releases.ubuntu.com/releases/22.04/ubuntu-22.04-live-server-amd64.iso