Since ACMEv1 with letsencrypt is going down next June, I was planning to switch to using Certbot on my Ubuntu 16.04.7.
Following the documentation, I installed snapd succesfully. However, when trying to install a snap, I get the following error :
error: system does not fully support snapd: cannot mount squashfs image using "squashfs": mount:
unknown filesystem type 'squashfs'
My snap version :
My searches on that issue gave me a few options :
- modprobe loop squashfuse :
modprobe: ERROR: ../libkmod/libkmod.c:514 lookup_builtin_file() could not open builtin file '/lib/modules/4.4.30-mod-std-ipv6-64/modules.builtin.bin'
- apt install fuse squashfuse : installs succesfully but still the error on snap install persists
The very strange thing is that snap is supposed to come preinstalled with Ubuntu 16.04. It wasn't, so I installed it myself, and can't get it running.
I noticed people talking about kernel updates.
My kernel is the following :
Should I try updating the kernel? If yes, where can I find the latest version and how can I install it without breaking everything (never did that before)?
If not, should I revert back to using apt install certbot?
Is it maintained?
Thanks in advance for your help.
I've never seen Ubuntu 16 without snap - and can only assume something went far off course during the installation.
That said, what is shown by:
sudo apt update
sudo apt upgrade
apt update :
Get:1 http://ubuntu.mirrors.ovh.net/ftp.ubuntu.com/ubuntu xenial InRelease [247 kB]
Get:2 http://ubuntu.mirrors.ovh.net/ftp.ubuntu.com/ubuntu xenial-updates InRelease [109 kB]
Get:3 http://ubuntu.mirrors.ovh.net/ftp.ubuntu.com/ubuntu xenial-backports InRelease [107 kB]
Hit:4 http://ppa.launchpad.net/nginx/stable/ubuntu xenial InRelease
Hit:5 http://ppa.launchpad.net/webupd8team/java/ubuntu xenial InRelease
Get:10 http://security.ubuntu.com/ubuntu xenial-security InRelease [109 kB]
Hit:11 https://deb.nodesource.com/node_8.x xenial InRelease
Ign:12 https://packages.elastic.co/beats/apt stable InRelease
Ign:7 https://packages.elastic.co/kibana/4.5/debian stable InRelease
Ign:8 https://packages.elastic.co/logstash/2.3/debian stable InRelease
Ign:9 https://packages.elastic.co/elasticsearch/2.x/debian stable InRelease
Get:16 https://packages.elastic.co/beats/apt stable Release [1,797 B]
Err:6 https://dl.yarnpkg.com/debian stable InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 23E7166788B63E1E
Get:13 https://packages.elastic.co/kibana/4.5/debian stable Release [1,797 B]
Get:14 https://packages.elastic.co/logstash/2.3/debian stable Release [3,301 B]
Get:15 https://packages.elastic.co/elasticsearch/2.x/debian stable Release [2,346 B]
Fetched 581 kB in 0s (749 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://dl.yarnpkg.com/debian stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 23E7166788B63E1E
W: http://packages.elastic.co/kibana/4.5/debian/dists/stable/Release.gpg: Signature by key 46095ACC8548582C1A2699A9D27D666CD88E42B4 uses weak digest algorithm (SHA1)
W: http://packages.elastic.co/logstash/2.3/debian/dists/stable/Release.gpg: Signature by key 46095ACC8548582C1A2699A9D27D666CD88E42B4 uses weak digest algorithm (SHA1)
W: Failed to fetch https://dl.yarnpkg.com/debian/dists/stable/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 23E7166788B63E1E
W: Some index files failed to download. They have been ignored, or old ones used instead.
As far as
apt upgrade is concerned, I just upgraded everything yesterday, and everything is up to date.
apt list --upgradable returns the empty listing
The upgrade broke some stuff that I had to took some time to fix and I'd rather not risk it again, hence the list instead.
Additional info that makes me think this may be kernel related : I have another machine on the exact same version (16.04.7) with the kernel
4.4.0-190-generic on which snap works fine.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.