Enable snaps to run before SSH comes up in classic boot process
Bug #1609762 reported by
Dan Watkins
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
snapd |
Confirmed
|
Medium
|
Unassigned |
Bug Description
A common pattern for daemons that are provided by cloud vendors (e.g. GCE, Windows Azure) is that they need to block some part of the boot to do configuration.
Most often, they need to run after networking is up but before SSH is up, to communicate with their metadata services to provision SSH configuration, so it would be good to solve that particular use case.
I could see this being solved in a couple of ways: either provide a specific way of specifying that we want to run before SSH is up, or provide a generic way of interleaving services in to the regular systemd boot process using unit names.