Comment 1 for bug 1978939

More testing and this is a bit more complicated, mainly because our chroot is based on core snap.
with the following change I was able to at least start the chroot
https://github.com/kubiko/snapd/commit/7bebc919789e3696e14eb1df6c45dfd70eb20c2b

however chroot is still not fully working, it fails when executing other binaries, see log:

2022/06/16 16:25:20.241252 daemon.go:247: started snapd/2.56+git1056.gdb27d5e (series 16; devmode) ubuntu-core/20 (armhf) linux/5.4.0-113-generic.
2022/06/16 16:25:20.252976 main.go:129: system does not fully support snapd: cannot mount squashfs image using "squashfs": fork/exec /usr/bin/mount: no such file or directory
2022/06/16 16:25:20.253874 daemon.go:340: adjusting startup timeout by 30s (pessimistic estimate of 30s plus 5s per snap)
2022/06/16 16:25:20.268111 devicemgr.go:321: no ubuntu-save mount
2022/06/16 16:25:20.554639 devicemgr.go:789: preload verified gadget metadata from seed failed: cannot run unsquashfs: fork/exec /usr/bin/unsquashfs: no such file or directory
cannot run daemon: state startup errors: [cannot obtain snap-seccomp version information: fork/exec /usr/lib/snapd/snap-seccomp: no such file or directory]