Yesterday I tried installing snapd on my Ubuntu 18.04 dedicated server, but after I did I had this error:
system does not fully support snapd: cannot mount squashfs image using “squashfs”: mount: /tmp/sanity-mountpoint-876234364: unknown filesystem type ‘squashfs’.
I though a reboot might help, so I rebooted my server. But then I was not able to access my remote server anymore. My hosting provider tried to ping it without success, so it automatically rebooted it in rescue mode. At first I thought that something was preventing my server to boot altogether, but after I connected to the rescue console, mounted the filesystem to have a look at syslog, I didn’t see anything suspicious. And then I found this topic that seems to indicate that there are known issues with snapd and certain kernel versions. So now I’m thinking that maybe my problem is just that my server takes too much time to boot, which triggers a premature reaction from my hosting provider’s monitoring system and doesn’t let snapd do its seeding.
Is that possible? If so, how can I fix that? Is it possible to manually neutralize or remove snapd from the boot sequence so that I can get access to my server again and update everything?