Snapd starts network-enabled snaps before networkd/netplan say the network is ready
Bug #1775724 reported by
Pavel Stratil
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
snapd |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
After hitting a problem with the lxd snap (see https:/
- lxd snap uses internally dnsmasq
- the 18.04 server install defaults to using systemd-resolved
- upon (re)boot, the lxd snap fails to start because of systemd-resolved not resolving shortly after boot, snapd doesn't wait for networkd/netplan to get ready.
To keep this bug report short, please kindly refer to https:/
Thanks for looking into this,
cheers, Pavel
Changed in snapd: | |
status: | New → Triaged |
importance: | Undecided → High |
To post a comment you must log in.
I had a look at a simple service snap: xkcd-webserver
This is a subset of the .service unit we generate:
zyga@x240:~$ cat /etc/systemd/ system/ snap.xkcd- webserver. xkcd-webserver. service
[Unit] target xkcd\x2dwebserv er-16.mount network.target
Wants=network.
After=snap-
As you can see we are waiting for "network.target" but not for "network- online. target" . If this is about being able to wait for "network- online. target" then I think this is a new feature request that we need to discuss and design.