Snap is unusable due to bad permissions

snapcraft
22

The issue is it’s mounted using FUSE and specific mount options that alter visible permissions:

Ah, that would explain the difference in permissions. We don’t have a mechanism to detect or correct this in Snapcraft. I can’t think of a programmatic way to do it, other than having the user change permissions in an override- script.

I never managed to run snapcraft with LXD on my machine directly because of (seemingly unsolvable) conflicts with my local Docker and dnsmasq.

Have you seen the suggestions here?

https://documentation.ubuntu.com/lxd/en/latest/howto/network_bridge_firewalld/#prevent-connectivity-issues-with-lxd-and-docker

Also, ppc64el and s390x failed to build because they apparently don’t have the gnome extension

I would limit where this snap builds with the platforms keyword.

However, the built snap wouldn’t run, giving me a segfault:

I have no idea how to debug this.

There is some relevant information here: https://snapcraft.io/docs/debug-snaps

I would start with looking at system logs related to snapd and apparmor, application logs (if your app is creating any before crashing), running in the environment where it was built, and then debugging the app itself (hooking up a debugger, adding log outputs, etc).

1 Like