StealthOS/subiquity
StealthOS
/
subiquity
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

services: run console-conf after core18.start-snapd.service 

On core18 the firstboot seeding happens via the core18.start-snapd
service. This service will do the initial start of snapd when the
system is unseeded. This service will wait until the system is
fully seeded.

We cannot run console-conf before that because it uses the "snap"
command which will not be available before the system is seeded.

Once that has landed https://github.com/snapcore/core18/pull/74
can be reverted (in fact the hooks/200-console-conf-after.chroot
file can be removed entirely).
This commit is contained in:
Michael Vogt 2018-10-12 09:39:44 +02:00 committed by Maciek Borzecki
parent 6c5c2022fd
commit fc224aab0c
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
debian/console-conf.console-conf@.service vendored
View File

@ -1,7 +1,7 @@
[Unit]
Description=Ubuntu Core Firstboot Configuration %I
After=systemd-user-sessions.service plymouth-quit-wait.service
After=rc-local.service
After=rc-local.service core18.start-snapd.service
IgnoreOnIsolate=yes
ConditionPathExists=/dev/tty0
ConditionPathExists=!/var/lib/console-conf/complete

2
debian/console-conf.serial-console-conf@.service vendored
View File

@ -2,7 +2,7 @@
Description=Ubuntu Core Firstboot Configuration %I
BindsTo=dev-%i.device
After=dev-%i.device systemd-user-sessions.service plymouth-quit-wait.service
After=rc-local.service
After=rc-local.service core18.start-snapd.service
ConditionPathExists=!/var/lib/console-conf/complete
StartLimitInterval=0