Argh, for some reason I stopped getting email notifications about posts to this thread an so missed a week’s worth of comments. Sorry about that.
There’s a lot of stuff here now and apologies if I miss something that’s been reported. I definitely encourage people to open bugs in Launchpad or start new threads here, it will be much easier to reply to everything that way.
That said
- there is an (embarrassing) bug around the network config not getting copied to the target system. That’s fixed in subiquity master and will be fixed in the next stable update today or tomorrow. The 50-curtin-networking.cfg file is a red herring, it’s confusing but not actually a problem. I’ll make a change to stop writing it.
- there should be no difference between UEFI and BIOS boots here, any differences would be a bug.
- as I think people realised, if you give http://x/y/z/ as a seed url, cloud-init tries to download from http://x/y/z/meta-data and http://x/y/z/user-data.
- if you are doing a purely net-based boot, you need to provide url=$path/to/install.iso on the kernel command line too
- I can’t reproduce that strange thing about interactive-sections: * vs a list of interactive-sections. I’ll keep trying though.
- “There is no way to verify your config beforehand” well there is a schema at https://wiki.ubuntu.com/FoundationsTeam/AutomatedServerInstalls/ConfigSchema but it’s not complete and there’s no very easy way to actually validate your user-data file against this yet, but it’s a start and we’ll make it easier to use.
- The documentation is incomplete in some places yes. This is a new thing though, it will improve.
- I’ll fix things so that you don’t need to pass --target to curtin in-target in late-commands.
I need to look into the apt config stuff, not sure what’s going on there.