Comment 3 for bug 2067284

Hi Nathan,

I had a closer look into craft-providers, and a mapping for the xenial images is missing.

When patching it in via

```
craft-providers on  main [$!] via 🐍 v2.7.18 (venv)
❯ git diff
diff --git a/craft_providers/lxd/remotes.py b/craft_providers/lxd/remotes.py
index 272722e..33e4ec2 100644
--- a/craft_providers/lxd/remotes.py
+++ b/craft_providers/lxd/remotes.py
@@ -123,6 +123,12 @@ class RemoteImage:

 # mapping from supported bases to actual lxd remote images
 _PROVIDER_BASE_TO_LXD_REMOTE_IMAGE: Dict[Enum, RemoteImage] = {
+ ubuntu.BuilddBaseAlias.XENIAL: RemoteImage(
+ image_name="xenial",
+ remote_name=BUILDD_RELEASES_REMOTE_NAME,
+ remote_address=BUILDD_RELEASES_REMOTE_ADDRESS,
+ remote_protocol=ProtocolType.SIMPLESTREAMS,
+ ),
     ubuntu.BuilddBaseAlias.BIONIC: RemoteImage(
         image_name="core18",
         remote_name=BUILDD_RELEASES_REMOTE_NAME,
```

I got a xenial build to kick off, but unfortunately, craft-providers uses a lot of snap(d) commands and flags, which do not seem to be present in the relevant version for xenial.

So IMHO this would need quite some investment from the starcraft team to make xenial work.

I will create an issue on their tracker and ask for feedback.