## The old image
$ lxc launch ubuntu-daily:21f94ea409ac cosmic-test
$ lxc exec cosmic-test -- sh -xc 'cat /etc/cloud/build.info; dpkg-query --show | pastebinit; systemd-analyze; systemd-analyze critical-chain'
+ cat /etc/cloud/build.info
build_name: server
serial: 20180928
+ dpkg-query --show
+ pastebinit http://paste.ubuntu.com/p/gyrNWkdSRG/
+ systemd-analyze
Startup finished in 11.822s (userspace)
graphical.target reached after 10.139s in userspace
+ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
## Try the current one.
$ lxc launch ubuntu-daily:cosmic c2
$ lxc exec c2 -- sh -xc 'cat /etc/cloud/build.info; dpkg-query --show | pastebinit; systemd-analyze; systemd-analyze critical-chain'
+ cat /etc/cloud/build.info
build_name: server
serial: 20181002
+ dpkg-query --show
+ pastebinit http://paste.ubuntu.com/p/MCkrygb9sM/
+ systemd-analyze
Startup finished in 38.639s (userspace)
graphical.target reached after 36.990s in userspace
+ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
The current squashfs/lxd image (20181002) is almost twice the size as the
previous image (20180928) and boots dramatically slower.
At first, just looking at manifests you'd blame systemd change, but I
think the real problem is seeded snaps.
$ lxc image list ubuntu-daily: | grep 18.10 | grep x86_64
| c (7 more) | 6cad1409aaac | yes | ubuntu 18.10 amd64 (daily) (20181002) | x86_64 | 323.85MB | Oct 2, 2018 at 12:00am (UTC) |
| | 21f94ea409ac | yes | ubuntu 18.10 amd64 (daily) (20180928) | x86_64 | 170.25MB | Sep 28, 2018 at 12:00am (UTC) |
| | 5011b07c621c | yes | ubuntu 18.10 amd64 (daily) (20180926) | x86_64 | 170.25MB | Sep 26, 2018 at 12:00am (UTC) |
## The old image daily:21f94ea40 9ac cosmic-test build.info; dpkg-query --show | pastebinit; systemd-analyze; systemd-analyze critical-chain' build.info paste.ubuntu. com/p/gyrNWkdSR G/
$ lxc launch ubuntu-
$ lxc exec cosmic-test -- sh -xc 'cat /etc/cloud/
+ cat /etc/cloud/
build_name: server
serial: 20180928
+ dpkg-query --show
+ pastebinit
http://
+ systemd-analyze
Startup finished in 11.822s (userspace)
graphical.target reached after 10.139s in userspace
+ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @10.139s seeded. service @6.041s +4.096s ─basic. target @5.698s
└─sockets. target @5.698s
└─snapd. socket @5.694s +3ms
└─ sysinit. target @5.682s
└─cloud- init.service @4.676s +1.003s
└─systemd- networkd- wait-online. service @1.659s +3.015s
└─systemd- networkd. service @1.608s +49ms
└ ─network- pre.target @1.605s
└─cloud- init-local. service @198ms +1.406s
└─systemd- journald. socket @187ms
└─ -.mount @184ms
└─system. slice @184ms
└─-.slice @184ms
└─multi-user.target @10.139s
└─snapd.
└─snapd.service @5.770s +269ms
└
## Try the current one. build.info; dpkg-query --show | pastebinit; systemd-analyze; systemd-analyze critical-chain' build.info paste.ubuntu. com/p/MCkrygb9s M/
$ lxc launch ubuntu-daily:cosmic c2
$ lxc exec c2 -- sh -xc 'cat /etc/cloud/
+ cat /etc/cloud/
build_name: server
serial: 20181002
+ dpkg-query --show
+ pastebinit
http://
+ systemd-analyze
Startup finished in 38.639s (userspace)
graphical.target reached after 36.990s in userspace
+ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @36.990s seeded. service @5.149s +31.839s ─snap-lxd- 8959.mount @15.227s +15ms
└─snap. mount @11.543s +14ms
└─local- fs-pre. target @363ms
└─ keyboard- setup.service @164ms +198ms
└─systemd- journald. socket @162ms
└─-.mount @159ms
└─system. slice @159ms
└ ─-.slice @159ms
└─multi-user.target @36.989s
└─snapd.
└─snapd.service @12.863s +67ms
└
Heres a diff of their manifests: manifest /tmp/20181002. manifest | grep "^[-+]" manifest 2018-10-04 12:16:28.593773558 -0400 manifest 2018-10-04 12:16:57.945328943 -0400 systemd: amd64 239-7ubuntu8 systemd: amd64 239-7ubuntu9 systemd: amd64 239-7ubuntu8 systemd: amd64 239-7ubuntu9 dispatcher 1.7-0ubuntu6 dispatcher 1.7-0ubuntu8
$ diff -u /tmp/20180928.
--- /tmp/20180928.
+++ /tmp/20181002.
-apparmor 2.12-4ubuntu7
+apparmor 2.12-4ubuntu8
-libapparmor1:amd64 2.12-4ubuntu7
+libapparmor1:amd64 2.12-4ubuntu8
-libnss-
+libnss-
-libpam-
+libpam-
-libsystemd0:amd64 239-7ubuntu8
+libsystemd0:amd64 239-7ubuntu9
-libudev1:amd64 239-7ubuntu8
+libudev1:amd64 239-7ubuntu9
-libzstd1:amd64 1.3.3+dfsg-2ubuntu1
+libzstd1:amd64 1.3.5+dfsg-1ubuntu1
-networkd-
+networkd-
-python3-configobj 5.0.6-2
+python3-configobj 5.0.6-3
-shared-mime-info 1.9-2
+shared-mime-info 1.10-1
-systemd 239-7ubuntu8
-systemd-sysv 239-7ubuntu8
+systemd 239-7ubuntu9
+systemd-sysv 239-7ubuntu9
-udev 239-7ubuntu8
+udev 239-7ubuntu9