This seems to be a "low resource" problem relating to snapd, assuming I'm seeing the same thing as didrocks. If I "systemctl mask snapd.seeded.service snapd.socket snapd.service" from e.g. a rescue shell, the installation proceeds normally.
That's with 1G of ram. If I use 4G then it works fine with snapd enabled.
This seems to be a "low resource" problem relating to snapd, assuming I'm seeing the same thing as didrocks. If I "systemctl mask snapd.seeded. service snapd.socket snapd.service" from e.g. a rescue shell, the installation proceeds normally.
That's with 1G of ram. If I use 4G then it works fine with snapd enabled.
Is this known (jibel?)?