A few more observations: 1) The output shown for the hook is just snapd debugging goo. It's not meaningful. 2) It is libc6 :(
You can demonstrate 2) by: starting a container with a known good image, removing lxd, upgrading libc6 & co and then running "snap install /var/lib/snapd/seed/snaps/lxd_21400.snap". I tried to strace snapd while the installing the lxd snap but that fails even with the old libc (probably because apparmor gets upset about something being ptraced?). snap install --devmode /var/lib/snapd/seed/snaps/lxd_21400.snap also fails, I don't know if that's surprising. If I hack the install hook out of the lxd snap, then it fails with a segfault in snap.lxd.activate.service. If I start the good image, let lxd seed properly, and then upgrade libc6, things are pretty broken: root@mwhudson-test-03:~# lxc 2021/09/24 03:34:20.355414 tool_linux.go:204: DEBUG: restarting into "/snap/snapd/current/usr/bin/snap" 2021/09/24 03:34:20.372561 cmd_run.go:410: DEBUG: SELinux not enabled 2021/09/24 03:34:20.372797 tracking.go:44: DEBUG: creating transient scope snap.lxd.lxc 2021/09/24 03:34:20.373178 tracking.go:176: DEBUG: session bus is not available: cannot find session bus 2021/09/24 03:34:20.373373 tracking.go:178: DEBUG: falling back to system bus 2021/09/24 03:34:20.374487 tracking.go:183: DEBUG: using system bus now, session bus was not available 2021/09/24 03:34:20.379914 tracking.go:305: DEBUG: created transient scope as object: /org/freedesktop/systemd1/job/1461 2021/09/24 03:34:20.380008 tracking.go:135: DEBUG: systemd could not associate process 2970 with transient scope snap.lxd.lxc.8787a98f-da32-4466-8105-764dc71b092b.scope 2021/09/24 03:34:20.380020 cmd_run.go:1170: DEBUG: snapd cannot track the started application 2021/09/24 03:34:20.380027 cmd_run.go:1171: DEBUG: snap refreshes will not be postponed by this process Segmentation fault But annoyingly the debugging aids all fail to work, e.g.: root@mwhudson-test-03:~# snap run --strace lxd.lxc 2021/09/24 03:35:26.821544 tool_linux.go:204: DEBUG: restarting into "/snap/snapd/current/usr/bin/snap" 2021/09/24 03:35:26.848119 cmd_run.go:410: DEBUG: SELinux not enabled 2021/09/24 03:35:26.848487 tracking.go:44: DEBUG: creating transient scope snap.lxd.lxc 2021/09/24 03:35:26.848719 tracking.go:176: DEBUG: session bus is not available: cannot find session bus 2021/09/24 03:35:26.848805 tracking.go:178: DEBUG: falling back to system bus 2021/09/24 03:35:26.849923 tracking.go:183: DEBUG: using system bus now, session bus was not available 2021/09/24 03:35:26.851652 tracking.go:305: DEBUG: created transient scope as object: /org/freedesktop/systemd1/job/1469 2021/09/24 03:35:26.851734 tracking.go:135: DEBUG: systemd could not associate process 3003 with transient scope snap.lxd.lxc.5d763d6a-a730-41bf-b6e3-6cd519cd1919.scope 2021/09/24 03:35:26.851742 cmd_run.go:1170: DEBUG: snapd cannot track the started application 2021/09/24 03:35:26.851748 cmd_run.go:1171: DEBUG: snap refreshes will not be postponed by this process error: exit status 1 Is it possible that snapd's own seccomp policies need updating? I guess I can try building a glibc with clone3 disabled and see what happens. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944004 Title: snapd.seeded.service never finishes on non-amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1944004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
