Snapcraft cleanbuild on Arch Linux with LXD - AppArmor permission error
Metadata
Current evaluation
⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.
Closed without resolution due to prolonged inactivity. The report detailed an AppArmor permission error during snapcraft cleanbuild on Arch Linux with LXD. No comments or fixes were provided, indicating the issue was abandoned or marked as invalid.
Suggested action: —
No scores available.
Issue body
I've been trying to set up a development environment for snaps on Arch Linux.
I've set up the following:
1. Installed snapd from AUR
2. Installed and enabled apparmor.service
3. Enable snapd.service and snapd.apparmor.service
4. Installed LXD from AUR
5. Configured permissions to allow unprivileged containers
5. Verified that LXD works by starting a couple of containers and checking network connectivity
6. Installed the snapcraft snap from edge/stable (tried both) channel
LXD and snap installation seems to work as expected, however whenever I try to run `snapcraft cleanbuild` I get the following error:
```
Creating snapcraft-parsimoniously-apostolic-flo
Starting snapcraft-parsimoniously-apostolic-flo
Waiting for a network connection...
Network connection established
Hit:1 http://archive.ubuntu.com/ubuntu xenial InRelease
Get:2 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB]
Get:3 http://archive.ubuntu.com/ubuntu xenial-backports InRelease [107 kB]
Get:4 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages [7532 kB]
Get:5 http://security.ubuntu.com/ubuntu xenial-security InRelease [109 kB]
Get:6 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages [627 kB]
Get:7 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 Packages [432 kB]
Get:8 http://archive.ubuntu.com/ubuntu xenial/universe Translation-en [4354 kB]
Get:9 http://security.ubuntu.com/ubuntu xenial-security/universe Translation-en [174 kB]
Get:10 http://security.ubuntu.com/ubuntu xenial-security/multiverse amd64 Packages [5604 B]
Get:11 http://security.ubuntu.com/ubuntu xenial-security/multiverse Translation-en [2676 B]
Get:12 http://archive.ubuntu.com/ubuntu xenial/multiverse amd64 Packages [144 kB]
Get:13 http://archive.ubuntu.com/ubuntu xenial/multiverse Translation-en [106 kB]
Get:14 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [926 kB]
Get:15 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages [742 kB]
Get:16 http://archive.ubuntu.com/ubuntu xenial-updates/universe Translation-en [307 kB]
Get:17 http://archive.ubuntu.com/ubuntu xenial-updates/multiverse amd64 Packages [16.7 kB]
Get:18 http://archive.ubuntu.com/ubuntu xenial-updates/multiverse Translation-en [8440 B]
Get:19 http://archive.ubuntu.com/ubuntu xenial-backports/main amd64 Packages [7280 B]
Get:20 http://archive.ubuntu.com/ubuntu xenial-backports/main Translation-en [4456 B]
Get:21 http://archive.ubuntu.com/ubuntu xenial-backports/universe amd64 Packages [7804 B]
Get:22 http://archive.ubuntu.com/ubuntu xenial-backports/universe Translation-en [4184 B]
Fetched 15.7 MB in 4s (3508 kB/s)
Reading package lists... Done
error: system does not fully support snapd: apparmor detected but insufficient permissions to use it
Stopping local:snapcraft-parsimoniously-apostolic-flo
An error occurred when trying to execute 'sudo snap set core refresh.hold=2019-03-29T19:44:38.135422Z' with 'lxd': returned exit code 1.
```
It seems to suggest that it has insufficient permissions to use apparmor inside the LXD build container. But I'm not exactly sure what it means in this context and if it's a bug or a configuration issue.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution due to prolonged inactivity. The report detailed an AppArmor permission error during snapcraft cleanbuild on Arch Linux with LXD. No comments or fixes were provided, indicating the issue was abandoned or marked as invalid. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed due to inactivity with no comments or resolution. The AppArmor permission error during snapcraft cleanbuild on Arch Linux with LXD remains unresolved and appears abandoned. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed due to inactivity without resolution. The AppArmor permission error during snapcraft cleanbuild on Arch Linux with LXD remains unfixed. No comments, workarounds, or follow-up actions were recorded. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1746612 Snapcraft cleanbuild doesn't work if you're not using the LXD snap | snapcraft (launchpad) | closed | Closed without resolution. Snapcraft hardcodes the LXD snap path during cleanbuild, causing failures with deb-installed LXD. The report appears abandoned or superseded by updated Snapcraft versions that dynamically detect LXD installations. | |
| #1666735 snapcraft cleanbuild does not work with lxd installed via snap | snapcraft (launchpad) | closed | Closed without resolution or merge. The report notes snapcraft cleanbuild fails to detect LXD installed via snap, suggesting checks via snap list or lxc list instead of apt cache. No fix was implemented or documented. | |
| #1697979 snapcraft fails on initial cleanbuild probe | snapcraft (launchpad) | closed | Closed without resolution. Snapcraft cleanbuild failed due to LXD connection errors when LXD was provided via a third-party snap alias. The report received no comments or fixes and was abandoned. | |
| #1800119 snapcraft cleanbuild | snapcraft (launchpad) | closed | Closed without resolution. The report details a PermissionError during snapcraft cleanbuild caused by restricted access to the .aptitude directory. With zero comments and no fix applied, the issue was abandoned or marked stale. | |
| #1752498 cleanbuild fails with lxd snap | snapcraft (launchpad) | closed | A user reported snapcraft cleanbuild failing with the LXD snap due to a FUSE mount permission error inside the container. With zero comments and years of inactivity, the report was abandoned and closed without a fix or resolution. | |
| #1703344 snapcraft cleanbuild exits with a traceback when lxd is not installed | snapcraft (launchpad) | closed | Closed without resolution. Missing LXD caused a FileNotFoundError during snapcraft cleanbuild. No comments, fixes, or status updates were provided. | |
| #1570706 Snapcraft cleanbuild command doesn't work | snapcraft (launchpad) | closed | Closed without resolution, likely abandoned or superseded. The cleanbuild command failed due to LXC hash format incompatibility and container stop errors. | |
| #1866300 snapcraft fails to build core20 snap | snapcraft (launchpad) | closed | Closed without comments or resolution after 74 days. The core20 build failure involving multipass hangs and LXD tracebacks was abandoned. | |
| #1750642 Snapcraft fails in LXD container on Debian 9 | snapcraft (launchpad) | closed | Closed as stale. The Snapcraft LXD container build failure on Debian 9 was not resolved due to outdated Debian and Snapcraft versions no longer being supported. | |
| #1896820 Snapcraft can't be run against a local or remote LXD project | snapcraft (launchpad) | open | Feature request from the LXD maintainer for snapcraft to support LXD projects (local/remote) for isolated or cluster-based builds. ~6 years old, no labels, zero comments, no maintainer response. Overlaps with remote LXD work tracked in snapcraft#4454. |