Public bug reported:
Snapd can't be started:
ubuntu@DESKTOP-V4DDKSS:~$ sudo /usr/lib/snapd/snapd
[sudo] password for ubuntu:
AppArmor status: apparmor not enabled
2019/03/27 10:36:05.383446 daemon.go:379: started snapd/2.37.4+18.10.1 (series
16; classic; devmode) ubuntu/18.10 (amd64) linux/4.4.0-17134-Microsoft.
2019/03/27 10:36:05.407044 main.go:123: system does not fully support snapd:
cannot mount squashfs image using "squashfs": mount:
/tmp/sanity-mountpoint-175479274: mount failed: Operation not permitted.
2019/03/27 10:36:10.413624 daemon.go:611: gracefully waiting for running hooks
2019/03/27 10:36:10.413702 daemon.go:613: done waiting for running hooks
daemon stop requested to wait for socket activation
Please fall back to using bind mount instead of using squashfs when
mounting squasfs images is not supported. (Bind mounts work in WSL.)
** Affects: snapd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821956
Title:
snapd can't start in WSL (Windows Subsystem for Linux)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1821956/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
