The image was working fine, and although the sheer amount of
experimentation and reinstalls makes my memory foggy, I do believe this
particular install had gone through a ubuntu-core update without any
issues. What caused the issue in the first place is a real networking
issue. I had placed the install within a DMZ that was wrongly
configured, so the clients of the subnet was unable to get a lease on an
IP-address. It was left on this subnet for quite some time and over
several boots. It now has internet access again, but the snap daemon
fails continuously. For what reason I'm unsure. I've seen different
reports of snap daemon failing because it starts before networking in
the boot process, maybe I'm suffering the same problem. This bug then,
would have surfaced due to a longer period of no network access for
I'm unfamiliar with journalctl and have yet to manage to get any form of
relevant info from a query. Maybe you could help me with some suggestions as to
what to search for in the journal?
The image is from https://people.canonical.com/~mvo/all-snaps/obsolete/, it was
downloaded on the 19th of September.
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
snapd fail on boot
To manage notifications about this bug go to:
ubuntu-bugs mailing list