Got an error today trying to use snap try in my lxd container:
Dec 18 23:27:08 staging systemd[1]: Reloading.
Dec 18 23:27:08 staging systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_sock>
Dec 18 23:27:09 staging systemd[1]: Reloading.
Dec 18 23:27:09 staging systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_sock>
Dec 18 23:27:09 staging systemd[1]: Mounting Mount unit for nextcloud, revision x1...
-- Subject: A start job for unit snap-nextcloud-x1.mount has begun execution
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A start job for unit snap-nextcloud-x1.mount has begun execution.
--
-- The job identifier is 48618.
Dec 18 23:27:09 staging mount[376807]: This doesn't look like a squashfs image.
Dec 18 23:27:09 staging systemd[1]: snap-nextcloud-x1.mount: Mount process exited, code=exited, status=255/EXCEPTION
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- An n/a= process belonging to unit snap-nextcloud-x1.mount has exited.
--
-- The process' exit code is 'exited' and its exit status is 255.
Dec 18 23:27:09 staging systemd[1]: snap-nextcloud-x1.mount: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The unit snap-nextcloud-x1.mount has entered the 'failed' state with result 'exit-code'.
Dec 18 23:27:09 staging systemd[1]: Failed to mount Mount unit for nextcloud, revision x1.
-- Subject: A start job for unit snap-nextcloud-x1.mount has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- A start job for unit snap-nextcloud-x1.mount has finished with a failure.
--
-- The job identifier is 48618 and the job result is failed.
Dec 18 23:27:09 staging systemd[1]: snapd.service: Got notification message from PID 376804, but reception only permitted for main PID 235
Dec 18 23:27:09 staging systemd[1]: Reloading.
Dec 18 23:27:09 staging systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_sock>
Dec 18 23:27:09 staging systemd[1]: Reloading.
Dec 18 23:27:09 staging systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_sock>
Dec 18 23:27:09 staging snapd[235]: taskrunner.go:271: [change 6 "Mount snap \"nextcloud\" (unset)" task] failed: [start snap-nextcloud-x1.mount] failed with exit status 1: Job failed. See "journalctl -xe">
Dec 18 23:27:10 staging systemd[1]: snapd.service: Got notification message from PID 376870, but reception only permitted for main PID 235
Dec 18 23:27:11 staging snapd[235]: handlers.go:496: Reported install problem for "nextcloud" as Crash report successfully submitted.
Dec 18 23:27:11 staging sudo[376728]: pam_unix(sudo:session): session closed for user root
This definitely used to work in the past.
Dec 18 23:27:09 staging mount[376807]: This doesn’t look like a squashfs image.
Well yeah… it’s not. Is this a known bug?
$ snap version
snap 2.48.1
snapd 2.48.1
series 16
ubuntu 20.04
kernel 5.4.0-58-generic
$ snap list
Name Version Rev Tracking Publisher Notes
core18 20201210 1944 latest/stable canonical✓ base
snapd 2.48.1 10492 latest/stable canonical✓ snapd