(f/document-launch-intent)⚡ % sudo SNAP_CONFINE_DEBUG=1 snap run anbox.container-manager                                                 ~/Work/android-in-a-box/anbox-upstream
DEBUG: security tag: snap.anbox.container-manager
DEBUG: executable:   /usr/lib/snapd/snap-exec
DEBUG: confinement:  non-classic
DEBUG: base snap:    core
DEBUG: apparmor label on snap-confine is: /usr/lib/snapd/snap-confine
DEBUG: apparmor mode is: enforce
DEBUG: checking if the current process shares mount namespace with the init process
DEBUG: re-associating is not required
DEBUG: creating lock directory /run/snapd/lock (if missing)
DEBUG: opening lock directory /run/snapd/lock
DEBUG: opening lock file: /run/snapd/lock/.lock
DEBUG: sanity timeout initialized and set for three seconds
DEBUG: acquiring exclusive lock (scope (global))
DEBUG: sanity timeout reset and disabled
DEBUG: ensuring that snap mount directory is shared
DEBUG: unsharing snap namespace directory
DEBUG: creating namespace group directory /run/snapd/ns
DEBUG: namespace group directory does not require intialization
DEBUG: releasing lock (scope: (global))
DEBUG: creating lock directory /run/snapd/lock (if missing)
DEBUG: opening lock directory /run/snapd/lock
DEBUG: opening lock file: /run/snapd/lock/anbox.lock
DEBUG: sanity timeout initialized and set for three seconds
DEBUG: acquiring exclusive lock (scope anbox)
DEBUG: sanity timeout reset and disabled
DEBUG: initializing mount namespace: anbox
DEBUG: opening namespace group directory /run/snapd/ns
DEBUG: attempting to re-associate the mount namespace with the namespace group anbox
DEBUG: successfully re-associated the mount namespace with the namespace group anbox
DEBUG: releasing resources associated with namespace group anbox
DEBUG: releasing lock (scope: anbox)
DEBUG: resetting PATH to values in sync with core snap
DEBUG: snappy_udev_init
DEBUG: creating user data directory: /root/snap/anbox/54
DEBUG: requesting changing of apparmor profile on next exec to snap.anbox.container-manager
DEBUG: loading bpf program for security tag snap.anbox.container-manager
DEBUG: read 48 bytes from /var/lib/snapd/seccomp/bpf//snap.anbox.container-manager.bin
DEBUG: raising privileges to load seccomp profile
DEBUG: dropping privileges after loading seccomp profile
DEBUG: execv(/usr/lib/snapd/snap-exec, /usr/lib/snapd/snap-exec...)
DEBUG:  argv[1] = anbox.container-manager
+ DATA_PATH=/var/snap/anbox/common/
+ ROOTFS_PATH=/var/snap/anbox/common//rootfs
+ ANDROID_IMG=/snap/anbox/54/android.img
+ [ ! -e /snap/anbox/54/android.img ]
+ start
+ mkdir -p /var/snap/anbox/common/lxc
+ /snap/anbox/54/bin/anbox-bridge.sh start
+ echo Y
+ tee /sys/module/fuse/parameters/userns_mounts
tee: /sys/module/fuse/parameters/userns_mounts: Permission denied
Y
+ echo WARNING: kernel doesn't support fuse in user namespaces
WARNING: kernel doesn't support fuse in user namespaces
+ AA_EXEC=/snap/anbox/54/usr/sbin/aa-exec -p unconfined --
+ [ ! -d /sys/kernel/security/apparmor ]
+ exec /snap/anbox/54/usr/sbin/aa-exec -p unconfined -- /snap/anbox/54/bin/anbox-wrapper.sh container-manager --data-path=/var/snap/anbox/common/ --android-image=/snap/anbox/54/android.img --daemon