It was nice to have LXD around and ready for many test/dev workloads, and I feel it was worth it back then. But we already replaced it with lxd-installer in minimal environments and it was fine there too. I never heard someone complaining that LXD takes a bit there, but every second of boot time seems to be valued highly.
Now that we had to reduce this to the lxd-installer everywhere (Due to LP #2051346) it is really worth to be re-revaluated. Thank you for driving this Phil! IMHO now that your first LXD command will take a bit longer already (due to fetching LXD snap), the exact amount of that "a bit longer" (as being more by also fetching snapd and base) seems almost irrelevant as long as it is in the same ballpark. On one hand those dev/test environments that use it most, can easily be made to tolerate the bit of extra time - they usually start with a barrage of other "install this" anyway that has the same "wait for network and install" characteristic. On the other hand reducing size and the initialization effort of it will save transfer and startup time for everyone - the guessed 3-5 seconds mentioned/assumed above would be totally worth it IMHO. --- Furthermore as Simon showed (thanks), by snapd being a baseless snap we'd not even gain something by having that around already for the latter fetch of lxd by lxd-installer. --- I further appreciate John's comment that we should back up some of our current assumptions (how much will this slow down lxc interactions, how much will the boot speed gain) with some actual data. But if that data will not totally upset what we expect, then I very much agree with Steve in comment #1 and would not optimize for it at the cost of all others and thereby I'd be fine to not preseed the other bits there. --- P.S. I wanted to mention that our perception might also be biased. I believe (no data) that the closer to Ubuntu development itself you are, the more likely you use LXD heavily in testing. But that same ratio likely does not apply to any user of Ubuntu images in the world. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2051572 Title: Always preseed core and snapd snap in server seed Status in ubuntu-meta package in Ubuntu: New Status in ubuntu-meta source package in Noble: New Bug description: In removing the LXD snap from preseeding in the server seed for Ubuntu 24.04 as part LP #2051346 [1] we also removed the snapd snap and the core22 snap. This means that are subsequent snap install, like LXD, will take much longer than expected for a non minimized image. Time taken to install LXD snap using the lxd-installer package without snapd and core22 preinstalled/seeded ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m29.107s user 0m0.006s sys 0m0.005s ``` Time taken to install LXD snap using the lxd-installer package with snapd and core22 already installed. ``` ubuntu@cloudimg:~$ time sudo lxd --version Installing LXD snap, please be patient. 5.19 real 0m15.034s user 0m0.005s sys 0m0.005s ``` This is a significant difference and for a workload we intend to remain as a core tested and tracked workload. As such I propose we re- introduce core22 and snapd snaps to our seed. LXD do intend to move to the core24 snap as their base as I'm sure snapd does too so when that does happen we need to update the preseeded core snap. This bug is to track the work of making that change in the server seed @ https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/tree/server#n69 [1] https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051346 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2051572/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
