Snapd errors when init isn't systemd

Is this a chromebook running a modified Ubuntu on top of Chrome OS?

if so, that’s likely why it’s not working. It’s not really Ubuntu. We don’t ship Ubuntu 18.04.2 with a 3.18 kernel. Unfortunately snaps won’t run on that device because we need features found in the supported kernels which are much newer than 3.18.

Sorry about that.

1 Like

it is a cromebook sorry to wast your time

2 Likes

one think that could use explaining is that i can download snap files through the terminal using snap commands. i just cant install them

Dear all,

I have the same issue. My Linux system is UserLAnd v2.7.2 on top of an Android 10 smartphone. My data are:

sandokan@localhost:~$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.5 LTS
Release:	18.04
Codename:	bionic
sandokan@localhost:~$ uname -a
Linux localhost 4.9.193-perf #2 SMP PREEMPT Fri Aug 7 23:10:49 IST 2020 aarch64 aarch64 aarch64 GNU/Linux
sandokan@localhost:~$ snap version
snap    2.47.1+18.04
snapd   unavailable
series  -
sandokan@localhost:~$ sudo systemctl start snapd
System has not been booted with systemd as init system (PID 1). Can't operate.
sandokan@localhost:~$ sudo snap install eclipse --classic
error: cannot communicate with server: Post http://localhost/v2/snaps/eclipse: dial unix /run/snapd.socket: connect: no such file or directory

Thanks for your time! :slight_smile: Dirk

systemd as init is currently a requirement to run snapd, it is unlikely you can make this work in that setup …

(base) grayson@gsb:~
$ lsb_release -a
No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux 10 (buster)
Release:	10
Codename:	buster

And

uname -a
Linux gsb 4.19.0-13-amd64 #1 SMP Debian 4.19.160-2 (2020-11-28) x86_64 GNU/Linux