← Back to issue list

cleanbuild fails with lxd snap

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1752498
Type
issue
State
closed
Author
~aleclarsen42
Labels
—
Created
Updated
Closed

Current evaluation

⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.

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.

Suggested action: —

No scores available.

Issue body

Hello, I am trying to run `snapcraft cleanbuild` on PureOS with the lxd snap, but it fails every time with: ``` $ snapcraft cleanbuild Creating snapcraft-superlaboriously-harmonious-vernon Starting snapcraft-superlaboriously-harmonious-vernon Waiting for a network connection... Network connection established Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB] Hit:2 http://archive.ubuntu.com/ubuntu xenial InRelease Get:3 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB] Get:4 http://security.ubuntu.com/ubuntu xenial-security/main Sources [116 kB] Get:5 http://archive.ubuntu.com/ubuntu xenial-backports InRelease [102 kB] Get:6 http://archive.ubuntu.com/ubuntu xenial/main Sources [868 kB] Get:7 http://security.ubuntu.com/ubuntu xenial-security/restricted Sources [2116 B] Get:8 http://security.ubuntu.com/ubuntu xenial-security/universe Sources [59.5 kB] Get:9 http://archive.ubuntu.com/ubuntu xenial/restricted Sources [4808 B] Get:10 http://security.ubuntu.com/ubuntu xenial-security/multiverse Sources [1516 B] Get:11 http://archive.ubuntu.com/ubuntu xenial/universe Sources [7728 kB] Get:12 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages [459 kB] Get:13 http://security.ubuntu.com/ubuntu xenial-security/main Translation-en [198 kB] Get:14 http://archive.ubuntu.com/ubuntu xenial/multiverse Sources [179 kB] Get:15 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages [7532 kB] Get:16 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 Packages [321 kB] Get:17 http://archive.ubuntu.com/ubuntu xenial/universe Translation-en [4354 kB] Get:18 http://security.ubuntu.com/ubuntu xenial-security/universe Translation-en [120 kB] Get:19 http://security.ubuntu.com/ubuntu xenial-security/multiverse amd64 Packages [3208 B] Get:20 http://archive.ubuntu.com/ubuntu xenial/multiverse amd64 Packages [144 kB] Get:21 http://archive.ubuntu.com/ubuntu xenial/multiverse Translation-en [106 kB] Get:22 http://archive.ubuntu.com/ubuntu xenial-updates/main Sources [298 kB] Get:23 http://archive.ubuntu.com/ubuntu xenial-updates/restricted Sources [2524 B] Get:24 http://security.ubuntu.com/ubuntu xenial-security/multiverse Translation-en [1408 B] Get:25 http://archive.ubuntu.com/ubuntu xenial-updates/universe Sources [191 kB] Get:26 http://archive.ubuntu.com/ubuntu xenial-updates/multiverse Sources [7968 B] Get:27 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [736 kB] Get:28 http://archive.ubuntu.com/ubuntu xenial-updates/main Translation-en [305 kB] Get:29 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages [592 kB] Get:30 http://archive.ubuntu.com/ubuntu xenial-updates/universe Translation-en [239 kB] Get:31 http://archive.ubuntu.com/ubuntu xenial-updates/multiverse amd64 Packages [16.2 kB] Get:32 http://archive.ubuntu.com/ubuntu xenial-updates/multiverse Translation-en [8052 B] Get:33 http://archive.ubuntu.com/ubuntu xenial-backports/main Sources [3432 B] Get:34 http://archive.ubuntu.com/ubuntu xenial-backports/universe Sources [4900 B] Get:35 http://archive.ubuntu.com/ubuntu xenial-backports/main amd64 Packages [4836 B] Get:36 http://archive.ubuntu.com/ubuntu xenial-backports/main Translation-en [3220 B] Get:37 http://archive.ubuntu.com/ubuntu xenial-backports/universe amd64 Packages [6624 B] Get:38 http://archive.ubuntu.com/ubuntu xenial-backports/universe Translation-en [3768 B] Fetched 24.9 MB in 8s (3094 kB/s) Reading package lists... Done Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically installed and is no longer required: libfreetype6 Use 'apt autoremove' to remove it. The following NEW packages will be installed: squashfuse 0 upgraded, 1 newly installed, 0 to remove and 7 not upgraded. Need to get 17.4 kB of archives. After this operation, 54.3 kB of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 squashfuse amd64 0.1.100-0ubuntu1~ubuntu16.04.1 [17.4 kB] Fetched 17.4 kB in 1s (9096 B/s) Selecting previously unselected package squashfuse. (Reading database ... 25549 files and directories currently installed.) Preparing to unpack .../squashfuse_0.1.100-0ubuntu1~ubuntu16.04.1_amd64.deb ... Unpacking squashfuse (0.1.100-0ubuntu1~ubuntu16.04.1) ... Processing triggers for man-db (2.7.5-1) ... Setting up squashfuse (0.1.100-0ubuntu1~ubuntu16.04.1) ... Looking up assertion ['account-key', 'public-key-sha3-384=BWDEoaqyr25nF5SNCvEv2v7QnM9QsfCc0PBMYD_i2NGSQ32EF2d4D0hqUel3m8ul'] Looking up assertion ['snap-declaration', 'snap-name=core'] Looking up assertion ['snap-revision', 'snap-revision=4110', 'snap-id=99T7MUlRhtI3U0QFgl5mXXESAiSwt776'] Adding assertion core_4110.assert Installing /run/core_4110.snap error: cannot perform the following tasks: - Mount snap "core" (4110) ([start snap-core-4110.mount] failed with exit status 1: Job for snap-core-4110.mount failed. See "systemctl status snap-core-4110.mount" and "journalctl -xe" for details. ) Stopping local:snapcraft-superlaboriously-harmonious-vernon The following command failed to run: 'snap install /run/core_4110.snap' exited with 1 ``` Unfortunately, the `--debug` flag doesn't seem to make a difference, but by stopping the process before it destroys the container, I can see the output of `systemctl status snap-core-4110.mount`: ``` $ lxc exec snapcraft-insuperably-epigenous-sunny -- /bin/bash -l mesg: ttyname failed: Success root@snapcraft-insuperably-epigenous-sunny:~# systemctl status snap-core-4110.mount ● snap-core-4110.mount - Mount unit for core Loaded: loaded (/etc/systemd/system/snap-core-4110.mount; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2018-03-01 05:55:22 UTC; 56s ago Where: /snap/core/4110 What: /var/lib/snapd/snaps/core_4110.snap Process: 1008 ExecMount=/bin/mount /var/lib/snapd/snaps/core_4110.snap /snap/core/4110 -t fuse.squashfuse -o nodev,ro,allow_other (code=exited, status=1/FAILURE) Mar 01 05:55:22 snapcraft-insuperably-epigenous-sunny systemd[1]: Mounting Mount unit for core... Mar 01 05:55:22 snapcraft-insuperably-epigenous-sunny mount[1008]: fusermount: mount failed: Operation not permitted Mar 01 05:55:22 snapcraft-insuperably-epigenous-sunny systemd[1]: snap-core-4110.mount: Mount process exited, code=exited status=1 Mar 01 05:55:22 snapcraft-insuperably-epigenous-sunny systemd[1]: Failed to mount Mount unit for core. Mar 01 05:55:22 snapcraft-insuperably-epigenous-sunny systemd[1]: snap-core-4110.mount: Unit entered failed state. ``` I am not sure what steps I should take to debug this issue further. Any help that you can provide would be greatly appreciated! Thanks!

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b — — 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.
qwen/qwen3.6-35b-a3b — — Closed without resolution or comments, likely abandoned due to inactivity or superseded by newer Snap/LXD versions. The original report detailed snapcraft cleanbuild failures with the LXD snap caused by a fusermount Operation not permitted error.
qwen3.6-35b-a3b-mtp-q6 — — Reported snapcraft cleanbuild failures with the LXD snap due to FUSE mount permission errors. Closed without resolution due to zero comments and extended inactivity, indicating abandonment or staleness.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#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.
78%
#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.
78%
#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.
78%
#1822372 Snapcraft cleanbuild on Arch Linux with LXD - AppArmor permission error snapcraft (launchpad) closed 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.
76%
#1570708 snapcraft should remove lxd container once finished the build snapcraft (launchpad) closed Requested automatic LXD container cleanup after snapcraft cleanbuild was closed without resolution. Zero comments and no implementation indicate the request was abandoned.
76%
#1624075 cleanbuild - Don't try to stop a non-existent container snapcraft (launchpad) closed Closed without resolution, likely abandoned. The report detailed snapcraft cleanbuild failing when attempting to stop a non-existent LXC container.
76%
#1700703 container builds fail after creating the container snapcraft (launchpad) closed Closed without comments or resolution. The LXD id mapping failure during snapcraft container builds was likely abandoned or superseded by newer container build implementations.
76%
#1788667 changes in snapd break lxd snap injection for cleanbuild snapcraft (launchpad) closed Abandoned. snapd permission changes to 0600 broke LXD snap injection for cleanbuild in unprivileged containers. No fix or workaround was implemented.
75%
#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.
74%
#1675516 can't cleanbuild snapcraft itself snapcraft (launchpad) closed Closed without resolution or comments, the report of a failed snapcraft cleanbuild due to missing build-packages was abandoned.
73%