Oracular buildd images lacked udev, breaking network setup; 25.04+ images were fixed, and #598 was closed after Oracular reached EOL.
Resolution: closed stale
Reason: Maintainer @mr-cal confirmed on 2025-03-12 that Plucky and newer were fixed; @lengau closed the issue on 2025-08-14 because Oracular was EOL. The underlying missing-udev image defect was tracked in launchpad/cloud-images#2092196, with no craft-providers resolving commit.
Evaluated by:mr-cal-bot
No scores available.
Issue body
### Bug Description
`ubuntu.BuilddBaseAlias.ORACULAR` and `ubuntu.BuilddBaseAlias.DEVEL` fail when launching a LXD container due to a problem with the `buildd` images and `systemd-resolved`.
Same as https://github.com/canonical/snapcraft/issues/4921
### To Reproduce
Run script below:
### part yaml
```shell
#! /usr/bin/env python3
from pathlib import Path
import logging
from craft_providers import bases, lxd
logging.basicConfig(level="DEBUG")
provider = lxd.LXDProvider(lxd_project="project1")
provider.ensure_provider_is_available()
alias = bases.BuilddBaseAlias.ORACULAR
my_base = bases.BuilddBase(alias=alias)
with provider.launched_environment(
project_name = "hello-world",
project_path = Path().absolute(),
base_configuration=my_base,
build_base=alias.value,
instance_name = "test-instance",
allow_unstable=True,
) as instance:
instance.execute_run(["ls"])
```
### Relevant log output
```shell
Failed to setup systemd-resolved.
* Command that failed: 'lxc --project snapcraft exec local:base-instance-snapcraft-buildd-base-v7-c-9d4e2b684569fe719a0d -- env CRAFT_MANAGED_MODE=1 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'
...
systemctl status systemd-resolved.service
× systemd-resolved.service - Network Name Resolution
Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Thu 2024-07-11 14:57:45 UTC; 37s ago
Invocation: fe747a54d0294da4af991ec064327654
Docs: man:systemd-resolved.service(8)
man:org.freedesktop.resolve1(5)
https://systemd.io/WRITING_NETWORK_CONFIGURATION_MANAGERS
https://systemd.io/WRITING_RESOLVER_CLIENTS
Main PID: 99 (code=exited, status=243/CREDENTIALS)
```
Evaluation history
Date
Model
Scores
Action
Summary
stealth/space-bunny-alpha
—
closed stale
Oracular buildd images lacked udev, breaking network setup; 25.04+ images were fixed, and #598 was closed after Oracular reached EOL.
qwen/qwen3.6-35b-a3b
—
closed resolved
Fixed in 25.04 (plucky) and newer cloud images. Oracular buildd images lacked the udev package, preventing systemd-networkd from configuring interfaces and causing systemd-resolved to fail. Issue closed as Oracular reached EOL.