Conversation
|
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 |
|
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. |
|
@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? |
|
Hi @stevenscg , yes. It could be caused by number of things: Firmware selection, process differs for each of them
Other issues that may cause you ending up in interactive shell could be influenced in the template by:
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. |
|
@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: |
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-datadefinition for cloud init as oppose to kickstart file for d-infs_udp: falseadded to synced folder as described in this issueSome 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