build-base: devel fails due to systemd-resolved issue in Ubuntu 26.04

Metadata

Project: snapcraft
Number: #6258
Type: issue
State: closed
Author: Hook25
Labels: —
Created: 2026-05-26 07:28 AM UTC
Updated: 2026-05-27 03:12 PM UTC
Closed: 2026-05-27 03:12 PM UTC

Current evaluation

Not a Snapcraft bug: reporter's jammy runners refreshed LXD to latest/stable 5.0.6, causing the systemd-resolved failure. Refreshing LXD to latest/beta restored builds; core26 uses no devel base.

Resolution: closed not a bug

Reason: Maintainer @mr-cal explained the core26 devel base was not used by Snapcraft 9 and pointed to canonical/core-base#447 awaiting promotion, suggesting latest/candidate meanwhile. The reporter then self-diagnosed the real cause: their Canonical jammy runners refreshed LXD to latest/stable 5.0.6 (not truly latest), and refreshing to latest/beta fixed the builds, so no Snapcraft change was made.

Evaluated by: mr-cal-bot

No scores available.

Issue body

### Check existing issues - [x] I've verified that this bug isn't described by any existing issues. ### Bug description When trying to build a core26 snap on the Canonical Self Hosted runners (jammy base) snapcraft fails with the following error: ``` Launching managed ubuntu devel instance... Creating new instance from remote Creating new base instance from remote Failed to setup systemd-resolved. * Command that failed: 'lxc --project snapcraft exec local:base-instance-snapcraft-buildd-base-v71--7ecce73048d4fe6c4262 -- env CRAFT_MANAGED_MODE=1 SNAPCRAFT_DEBUG=False SNAPCRAFT_BUILD_ENVIRONMENT=lxd SNAPCRAFT_LXD_REMOTE=local SNAPCRAFT_LAUNCHPAD_INSTANCE=production \'SNAPCRAFT_IMAGE_INFO={"build_url":"https://github.com/canonical/checkbox/actions/runs/26438171369"}\' SNAPCRAFT_BUILD_INFO=1 DEBIAN_FRONTEND=noninteractive DEBCONF_NONINTERACTIVE_SEEN=true DEBIAN_PRIORITY=critical systemctl restart systemd-resolved' * Command exit code: 1 * Command standard error output: b'Job for systemd-resolved.service failed because the control process exited with error code.\nSee "systemctl status systemd-resolved.service" and "journalctl -xeu systemd-resolved.service" for details.\n' Full execution log: '/home/ubuntu/.local/state/snapcraft/log/snapcraft-20260526-071942.947141.log' ``` This seems related to: https://github.com/canonical/snapcraft/issues/4921 ### Steps to reproduce 1. Create core26 snap (devel base) 2. Refresh snapcraft to 9.x/beta 3. Build it ### Environment Canonical SHR: amd64-large-ps7-2-34ecd1d50bf4 (jammy amd64) using snapcore/action-build@v1.3.0 build snap action. Installation log: ``` Installing Snapcraft plus dependencies Ensuring ubuntu is in the lxd group... /usr/bin/sudo groupadd --force --system lxd /usr/bin/sudo usermod --append --groups lxd ubuntu Installing LXD... /usr/bin/sudo snap refresh lxd lxd (5.0/stable) 5.0.6-7fc3b36 from Canonical** refreshed Initialising LXD... /usr/bin/sudo lxd init --auto Installed docker related packages might interfere with LXD networking: /usr/bin/sudo iptables -P FORWARD ACCEPT Installing Snapcraft... /usr/bin/sudo snap install --channel 9.x/beta --classic snapcraft snapcraft (9.x/beta) 9.0.0 from Canonical** installed /usr/bin/sudo -u ubuntu -E snapcraft ``` ### snapcraft.yaml ```yaml (probably not relevant to this issue, core26 based snap, devel) ``` ### Log output ```shell Installing Snapcraft plus dependencies Ensuring ubuntu is in the lxd group... /usr/bin/sudo groupadd --force --system lxd /usr/bin/sudo usermod --append --groups lxd ubuntu Installing LXD... /usr/bin/sudo snap refresh lxd lxd (5.0/stable) 5.0.6-7fc3b36 from Canonical** refreshed Initialising LXD... /usr/bin/sudo lxd init --auto Installed docker related packages might interfere with LXD networking: /usr/bin/sudo iptables -P FORWARD ACCEPT Installing Snapcraft... /usr/bin/sudo snap install --channel 9.x/beta --classic snapcraft snapcraft (9.x/beta) 9.0.0 from Canonical** installed /usr/bin/sudo -u ubuntu -E snapcraft Running snapcraft without a command will not be possible in future releases. Use 'snapcraft pack' instead. Launching managed ubuntu devel instance... Creating new instance from remote Creating new base instance from remote Failed to setup systemd-resolved. * Command that failed: 'lxc --project snapcraft exec local:base-instance-snapcraft-buildd-base-v71--7ecce73048d4fe6c4262 -- env CRAFT_MANAGED_MODE=1 SNAPCRAFT_DEBUG=False SNAPCRAFT_BUILD_ENVIRONMENT=lxd SNAPCRAFT_LXD_REMOTE=local SNAPCRAFT_LAUNCHPAD_INSTANCE=production \'SNAPCRAFT_IMAGE_INFO={"build_url":"https://github.com/canonical/checkbox/actions/runs/26438171369"}\' SNAPCRAFT_BUILD_INFO=1 DEBIAN_FRONTEND=noninteractive DEBCONF_NONINTERACTIVE_SEEN=true DEBIAN_PRIORITY=critical systemctl restart systemd-resolved' * Command exit code: 1 * Command standard error output: b'Job for systemd-resolved.service failed because the control process exited with error code.\nSee "systemctl status systemd-resolved.service" and "journalctl -xeu systemd-resolved.service" for details.\n' Full execution log: '/home/ubuntu/.local/state/snapcraft/log/snapcraft-20260526-071942.947141.log' ```

Evaluation history

Date	Model	Scores	Action	Summary
2026-10-03 01:38 PM UTC	stealth/space-bunny-alpha	—	closed not a bug	Not a Snapcraft bug: reporter's jammy runners refreshed LXD to latest/stable 5.0.6, causing the systemd-resolved failure. Refreshing LXD to latest/beta restored builds; core26 uses no devel base.
2026-09-25 09:15 AM UTC	stealth/space-bunny-alpha	—	closed not a bug	Reporter traced the failure to Jammy runners refreshing LXD to latest/stable 5.0.6; switching the CI refresh to latest/beta restored builds, requiring no Snapcraft change.
2026-09-14 03:49 AM UTC	qwen/qwen3.6-35b-a3b	—	—	The systemd-resolved failure on Ubuntu 26.04 devel was resolved by the author. An incorrect LXD refresh on jammy runners caused the issue. Updating the CI workflow to use latest/beta fixed the builds.
2026-07-23 03:55 PM UTC	qwen/qwen3.6-35b-a3b	—	—	Resolved by the author. The build failure stemmed from an outdated LXD version on jammy runners. Refreshing LXD to latest/beta fixed the systemd-resolved setup error, allowing builds to succeed. Issue closed.
2026-07-22 02:16 PM UTC	qwen/qwen3.6-35b-a3b	—	—	Resolved by author via CI configuration fix. The systemd-resolved build failure stemmed from an outdated LXD version in the runner, not a snapcraft defect. Refreshing LXD to latest/beta in the pipeline fixed the error, enabling successful core26 builds. Issue closed.
2026-07-04 04:24 PM UTC	qwen3.6-35b-a3b-mtp-q6	—	—	Closed by author. The systemd-resolved build failure resulted from a CI configuration issue refreshing LXD to an outdated latest version on jammy runners. Resolved by explicitly refreshing LXD to latest/beta.

Update history

No update history recorded yet.

Related work

Related To: canonical/snapcraft#4921 (confidence 85%)
Referenced by the reporter as a similar build-base: devel systemd-resolved failure; previously fixed by PR #5297 (65a6004f).
Related To: core-base#447 (confidence 70%)
Cited by mr-cal as the core26 image fix awaiting promotion to latest/stable; Snapcraft 9 stopped using the devel base for core26.

Related issues

Issue	Project	State	Summary	Similarity
#2017515 build-base devel does not work when ubuntu-daily:devel is not available	snapcraft (launchpad)	closed	No Snapcraft fix was needed: the ubuntu-daily:devel image alias was repointed to 23.04 by Ubuntu infrastructure (toabctl, 2023-05-02) and the reporter confirmed build-base: devel builds worked again.	74%
#4921 `build-base: devel` fails due to `systemd-resolved` issue in Ubuntu 24.10	snapcraft	closed	Corrected Ubuntu images restored build-base: devel; PR #5297 (65a6004f5) re-enabled devel spread tests and resolved the regression.	73%
#6282 Job for systemd-resolved.service failed because the control process exited with error code	snapcraft	open	snapcraft 9.0.0 pack --use-lxd fails on Ubuntu 26.04 when restarting systemd-resolved in the core24 buildd container; maintainer cannot reproduce and has requested confirmation.	73%