← Back to issue list

snapcraft fails on initial cleanbuild probe

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1697979
Type
issue
State
closed
Author
~lazypower
Labels
Created
Updated
Closed

Current evaluation

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

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.

Suggested action:

No scores available.

Issue body

I was attempting to build a new snap via 'snapcraft cleanbuild' on rev 2.29. Notables: my lxd install is an alias from another snap package providing lxd. I'm not certain if this is intended to work or if it will ever work due to it being a third party lxd package. charles@carbon:~/work/snaps/rtorrent$ snap aliases Command Alias Notes conjure-up.conjure-down conjure-down - conjure-up.juju juju - conjure-up.lxc lxc manual My test was unsuccessful via a message complaining that the command completed unsuccessfully: $ snapcraft cleanbuild --debug Starting snapcraft 2.29 from /usr/lib/python3/dist-packages/snapcraft. Setting up part 'rtorrent' with plugin 'cmake' and properties {'build-packages': ['libcurl', 'libncurses5'], 'snap': [], 'source': 'https://github.com/rakshasa/rtorrent.git', 'plugin': 'cmake', 'stage': [], 'prime': []}. Connection refused; is LXD running? Traceback (most recent call last): File "/usr/lib/python3/dist-packages/snapcraft/internal/lxd.py", line 229, in _verify_remote check_output(['lxc', 'list', '{}:'.format(remote)]) File "/usr/lib/python3.5/subprocess.py", line 626, in check_output **kwargs).stdout File "/usr/lib/python3.5/subprocess.py", line 708, in run output=stdout, stderr=stderr) subprocess.CalledProcessError: Command '['lxc', 'list', 'local:']' returned non-zero exit status 1 The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/bin/snapcraft", line 31, in <module> snapcraft.main.main() File "/usr/lib/python3/dist-packages/snapcraft/main.py", line 253, in main return run(args, project_options) File "/usr/lib/python3/dist-packages/snapcraft/main.py", line 295, in run lifecycle.cleanbuild(project_options, remote=args['--remote']), File "/usr/lib/python3/dist-packages/snapcraft/internal/lifecycle.py", line 344, in cleanbuild metadata=config.get_metadata(), remote=remote).execute() File "/usr/lib/python3/dist-packages/snapcraft/internal/lxd.py", line 143, in __init__ container_name=container_name, remote=remote) File "/usr/lib/python3/dist-packages/snapcraft/internal/lxd.py", line 53, in __init__ _verify_remote(remote) File "/usr/lib/python3/dist-packages/snapcraft/internal/lxd.py", line 237, in _verify_remote '#multiple-hosts'.format(remote)) from e snapcraft.internal.errors.SnapcraftEnvironmentError: There are either no permissions or the remote 'local' does not exist. Verify the existing remotes by running `lxc remote list` To setup a new remote, follow the instructions at https://linuxcontainers.org/lxd/getting-started-cli/#multiple-hosts $ lxc list local: +---------------+---------+------+------+------------+-----------+ | NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS | +---------------+---------+------+------+------------+-----------+ | juju-2bad81-0 | STOPPED | | | PERSISTENT | 0 | +---------------+---------+------+------+------------+-----------+ $ lxc remote list +-----------------+------------------------------------------+---------------+--------+--------+ | NAME | URL | PROTOCOL | PUBLIC | STATIC | +-----------------+------------------------------------------+---------------+--------+--------+ | images | https://images.linuxcontainers.org | simplestreams | YES | NO | +-----------------+------------------------------------------+---------------+--------+--------+ | local (default) | unix:// | lxd | NO | YES | +-----------------+------------------------------------------+---------------+--------+--------+ | ubuntu | https://cloud-images.ubuntu.com/releases | simplestreams | YES | YES | +-----------------+------------------------------------------+---------------+--------+--------+ | ubuntu-daily | https://cloud-images.ubuntu.com/daily | simplestreams | YES | YES | +-----------------+------------------------------------------+---------------+--------+--------+

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b 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.
qwen/qwen3.6-35b-a3b Abandoned. The report details a snapcraft cleanbuild failure caused by an LXD connection error during the initial probe, despite the LXD daemon being accessible via CLI. No comments or fixes were provided.
qwen3.6-35b-a3b-mtp-q6 Closed without resolution. The cleanbuild LXD integration was abandoned and later deprecated in snapcraft. No fix was implemented.

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.
85%
#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.
85%
#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.
81%
#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.
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.
78%
#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.
78%
#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.
77%
#1859469 snapcraft lxd + snapd transition in progress snapcraft (launchpad) closed Closed as non-reproducible and abandoned. The snapcraft lxd command failed due to a snapd transition conflict, but the issue was resolved in version 3.8 and later.
75%
#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.
75%
#1890965 snapcraft --use-lxd is broken snapcraft (launchpad) closed Closed without a documented fix. The hardcoded LXD image URL returning 404 broke CI. Likely abandoned or resolved upstream.
74%