I followed the instructions at https://docs.snapcraft.io/build-snaps/build-on-lxd-docker. All default options for sudo lxd init. My user is part of the lxd group, and I restarted my computer between running sudo lxd init and the lxc commands. The problem is that lxc exec snapcraft -- snap install snapcraft --classic errors out.
I know that snapcraft is available via the package manager under Ubuntu 16.04+, but I get glibc errors if I build on anything other than 16.04. I would rather use lxc than do a full reinstall to 16.04 just so that I can build my dependencies to be compatible with the 16.04 core used by snap. Is it possible to use a version of Ubuntu other than 16.04 as the base for a snap?
What are my options here? The snap requires webgl, so I can’t use VirtualBox which doesn’t seem to support webgl in Linux guests.
[amiller@amiller-All-Series ~]$ lxc launch ubuntu:16.04 snapcraft -c security.privileged=true
Creating snapcraft
Starting snapcraft
[amiller@amiller-All-Series ~]$ lxc config device add snapcraft homedir disk source=/home/$USER path=/home/ubuntu
Device homedir added to snapcraft
[amiller@amiller-All-Series ~]$ lxc exec snapcraft -- snap install snapcraft --classic
error: cannot perform the following tasks:
- Mount snap "core" (4206) ([start snap-core-4206.mount] failed with exit status 1: Job for snap-core-4206.mount failed. See "systemctl status snap-core-4206.mount" and "journalctl -xe" for details.
)
[amiller@amiller-All-Series ~]$ lxc exec snapcraft -- systemctl status snap-core-4206.mount
â—Ź snap-core-4206.mount - Mount unit for core
Loaded: loaded (/etc/systemd/system/snap-core-4206.mount; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2018-03-29 20:55:15 UTC; 1min 18s ago
Where: /snap/core/4206
What: /var/lib/snapd/snaps/core_4206.snap
Process: 578 ExecMount=/bin/mount /var/lib/snapd/snaps/core_4206.snap /snap/core/4206 -t squashfs -o nodev,ro (code=exited, status=32)
Mar 29 20:55:15 snapcraft systemd[1]: Mounting Mount unit for core...
Mar 29 20:55:15 snapcraft mount[578]: mount: /snap/core/4206: mount failed: Unknown error -1
Mar 29 20:55:15 snapcraft systemd[1]: snap-core-4206.mount: Mount process exited, code=exited status=32
Mar 29 20:55:15 snapcraft systemd[1]: Failed to mount Mount unit for core.
Mar 29 20:55:15 snapcraft systemd[1]: snap-core-4206.mount: Unit entered failed state.
[amiller@amiller-All-Series ~]$ lxc exec snapcraft -- journalctl -xe
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/snapd.service: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/sys-kernel-debug.mount: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/dev-lxd.mount: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/accounts-daemon.service: Operation not permitted
Mar 29 20:55:15 snapcraft mount[578]: mount: /snap/core/4206: mount failed: Unknown error -1
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/dev-ptmx.mount: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/rsyslog.service: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/proc-swaps.mount: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/resolvconf.service: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/rc-local.service: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/ondemand.service: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/dev-net-tun.mount: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/systemd-update-utmp.service: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/dbus.service: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/dev-fuse.mount: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/lvm2-monitor.service: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/open-iscsi.service: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/system-getty.slice: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/proc-stat.mount: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/lxd-containers.service: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/systemd-user-sessions.service: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/proc-uptime.mount: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/iscsid.service: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/cloud-config.service: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/home-ubuntu.mount: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/sys-fs-fuse-connections.mount: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/proc-meminfo.mount: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/proc-diskstats.mount: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/cron.service: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/apport.service: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/systemd-journal-flush.service: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/polkitd.service: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/unattended-upgrades.service: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/proc-sysrq\x2dtrigger.mount: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/systemd-tmpfiles-setup.service: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/systemd-random-seed.service: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/cloud-init.service: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/var-lib-lxcfs.mount: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/networking.service: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/dev-.lxd\x2dmounts.mount: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/proc-sys-net.mount: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/cloud-final.service: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/systemd-journald.service: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/-.mount: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/proc-sys-fs-binfmt_misc.mount: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/dev-mqueue.mount: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/irqbalance.service: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/mdadm.service: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/ssh.service: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/atd.service: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/ufw.service: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/sys-devices-virtual-net.mount: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/cloud-init-local.service: Operation not permitted
Mar 29 20:55:15 snapcraft systemd[1]: snap-core-4206.mount: Mount process exited, code=exited status=32
Mar 29 20:55:15 snapcraft systemd[1]: Failed to mount Mount unit for core.
-- Subject: Unit snap-core-4206.mount has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit snap-core-4206.mount has failed.
--
-- The result is failed.
Mar 29 20:55:15 snapcraft systemd[1]: snap-core-4206.mount: Unit entered failed state.
Mar 29 20:55:17 snapcraft snapd[324]: 2018/03/29 20:55:17.204218 handlers.go:310: Reported install problem for "core" as 7bf00916-3393-11e8-b13c-fa163e839e11 OOPSID
[amiller@amiller-All-Series ~]$
I wasn’t sure if I should install squashfuse on the host or in the container, so I tried both and squashfuse successfully installed on the host. The snapcraft snap still fails to install in the container. I’m not sure if this is a problem or not because I can use the Ubuntu 16.04 container to build my application’s libraries, but I will have to call snapcraft from the 17.10 or 18.04 host to do its packaging magic. If this procedure works and doesn’t produce snaps with version-specific bugs in their native libraries then I’ll go with it. It just seems unsafe to not follow the instructions at https://docs.snapcraft.io/build-snaps/build-on-lxd-docker.
Terminal history
[amiller@amiller-All-Series ~]$ sudo apt install squashfuse
[sudo] password for amiller:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
squashfuse
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 17.5 kB of archives.
After this operation, 54.3 kB of additional disk space will be used.
Get:1 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 squashfuse amd64 0.1.100-0ubuntu2 [17.5 kB]
Fetched 17.5 kB in 0s (71.8 kB/s)
Selecting previously unselected package squashfuse.
(Reading database ... 226117 files and directories currently installed.)
Preparing to unpack .../squashfuse_0.1.100-0ubuntu2_amd64.deb ...
Unpacking squashfuse (0.1.100-0ubuntu2) ...
Setting up squashfuse (0.1.100-0ubuntu2) ...
Processing triggers for man-db (2.7.6.1-2) ...
[amiller@amiller-All-Series ~]$ lxc exec snapcraft -- apt install squashfuse
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package squashfuse
[amiller@amiller-All-Series ~]$ lxc exec snapcraft -- snap install snapcraft --classic
error: cannot perform the following tasks:
- Mount snap "core" (4206) ([start snap-core-4206.mount] failed with exit status 1: Job for snap-core-4206.mount failed. See "systemctl status snap-core-4206.mount" and "journalctl -xe" for details.
)
[amiller@amiller-All-Series ~]$ lxc exec snapcraft -- systemctl status snap-core-4206.mount
â—Ź snap-core-4206.mount - Mount unit for core
Loaded: loaded (/etc/systemd/system/snap-core-4206.mount; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2018-03-30 02:02:06 UTC; 19s ago
Where: /snap/core/4206
What: /var/lib/snapd/snaps/core_4206.snap
Process: 834 ExecMount=/bin/mount /var/lib/snapd/snaps/core_4206.snap /snap/core/4206 -t squashfs -o nodev,ro (code=exited, status=32)
Mar 30 02:02:06 snapcraft systemd[1]: Mounting Mount unit for core...
Mar 30 02:02:06 snapcraft mount[834]: mount: /snap/core/4206: mount failed: Unknown error -1
Mar 30 02:02:06 snapcraft systemd[1]: snap-core-4206.mount: Mount process exited, code=exited status=32
Mar 30 02:02:06 snapcraft systemd[1]: Failed to mount Mount unit for core.
Mar 30 02:02:06 snapcraft systemd[1]: snap-core-4206.mount: Unit entered failed state.
[amiller@amiller-All-Series ~]$ lxc exec snapcraft -- journalctl -xe
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/proc-diskstats.mount: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/home-ubuntu.mount: Operation not permitted
Mar 30 02:02:06 snapcraft mount[834]: mount: /snap/core/4206: mount failed: Unknown error -1
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/proc-meminfo.mount: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/rsyslog.service: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/proc-sys-net.mount: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/iscsid.service: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/polkitd.service: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/systemd-journal-flush.service: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/systemd-random-seed.service: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/-.mount: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/proc-swaps.mount: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/sys-kernel-debug-tracing.mount: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/dev-net-tun.mount: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/apport.service: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/ssh.service: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/snapd.service: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/proc-uptime.mount: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/dev-.lxd\x2dmounts.mount: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/dev-lxd.mount: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/proc-stat.mount: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/sys-fs-fuse-connections.mount: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/proc-sysrq\x2dtrigger.mount: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/rc-local.service: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/dev-mqueue.mount: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/systemd-update-utmp.service: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/resolvconf.service: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/dev-ptmx.mount: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/systemd-logind.service: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/unattended-upgrades.service: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/cloud-init-local.service: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/system-getty.slice: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/ondemand.service: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/console-getty.service: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/accounts-daemon.service: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/irqbalance.service: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/systemd-tmpfiles-setup.service: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/cloud-final.service: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/cron.service: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/networking.service: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/mdadm.service: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/proc-sys-fs-binfmt_misc.mount: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/proc-cpuinfo.mount: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/ufw.service: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/dev-fuse.mount: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/sys-kernel-debug.mount: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/apparmor.service: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/systemd-journald.service: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/atd.service: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/sys-devices-virtual-net.mount: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/cloud-init.service: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/systemd-user-sessions.service: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: Failed to reset devices.list on /system.slice/var-lib-lxcfs.mount: Operation not permitted
Mar 30 02:02:06 snapcraft systemd[1]: snap-core-4206.mount: Mount process exited, code=exited status=32
Mar 30 02:02:06 snapcraft systemd[1]: Failed to mount Mount unit for core.
-- Subject: Unit snap-core-4206.mount has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit snap-core-4206.mount has failed.
--
-- The result is failed.
Mar 30 02:02:06 snapcraft systemd[1]: snap-core-4206.mount: Unit entered failed state.
Mar 30 02:02:07 snapcraft snapd[308]: 2018/03/30 02:02:07.241557 handlers.go:310: Reported install problem for "core" as 593346d8-33be-11e8-b826-fa163e54c21f OOPSID
[amiller@amiller-All-Series ~]$ which squashfuse
/usr/bin/squashfuse
[amiller@amiller-All-Series ~]$
Thanks, that mostly solved my problem. After just running apt update && apt upgrade, the snapcraft snap still failed to install in the container:
root@snapcraft:~# apt install squashfuse
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
libfreetype6
Use 'apt autoremove' to remove it.
The following NEW packages will be installed:
squashfuse
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 17.4 kB of archives.
After this operation, 54.3 kB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 squashfuse amd64 0.1.100-0ubuntu1~ubuntu16.04.1 [17.4 kB]
Fetched 17.4 kB in 0s (68.6 kB/s)
Selecting previously unselected package squashfuse.
(Reading database ... 25552 files and directories currently installed.)
Preparing to unpack .../squashfuse_0.1.100-0ubuntu1~ubuntu16.04.1_amd64.deb ...
Unpacking squashfuse (0.1.100-0ubuntu1~ubuntu16.04.1) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up squashfuse (0.1.100-0ubuntu1~ubuntu16.04.1) ...
root@snapcraft:~# snap install snapcraft --classic
error: cannot perform the following tasks:
- Setup snap "core" (4206) security profiles (cannot setup udev for snap "core": cannot reload udev rules: exit status 2
udev output:
)
- Setup snap "core" (4206) security profiles (cannot reload udev rules: exit status 2
udev output:
)
root@snapcraft:~# exit
I was able to fix this though by then running:
amiller@amiller-MS-7A70:~$ lxc stop snapcraft
amiller@amiller-MS-7A70:~$ lxc start snapcraft
amiller@amiller-MS-7A70:~$ lxc exec snapcraft -- bash
root@snapcraft:~# snap install snapcraft --classic
2018-03-30T05:42:43Z INFO Waiting for restart...
snapcraft 2.40 from 'canonical' installed
root@snapcraft:~# snapcraft --help
Usage: snapcraft [OPTIONS] COMMAND [ARGS]...
Snapcraft is a delightful packaging tool.
Thanks for the help! Now I can update my snap more frequently because I don’t have to boot into an older version of Ubuntu to build.
Yeah, that happens to me sometimes too, where I need to reboot to get snaps working in a container. I’m not sure if it relates to squashfuse first being installed or what, but it doesn’t seem 100% consistent. @zyga-snapd might have some clues.
