build-base: devel fails due to systemd-resolved issue in Ubuntu 26.04
Metadata
Current evaluation
⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.
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.
Suggested action: —
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 |
|---|---|---|---|---|
| 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. | |
| 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. | |
| 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 issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #4921 `build-base: devel` fails due to `systemd-resolved` issue in Ubuntu 24.10 | snapcraft | closed | Resolved by updating craft-providers to fix the systemd-resolved crash in Ubuntu 24.10 buildd images. The devel build base now functions correctly. Spread tests are pending re-enablement. |