@mr_cal, sorry for the late reply, somehow your reply did not get to my inbox.
Yes, I was able to reproduce it, exit code 2.
@mr_cal, sorry for the late reply, somehow your reply did not get to my inbox.
Yes, I was able to reproduce it, exit code 2.
The info of one of the instances:
Name: base-instance-snapcraft-buildd-base-v7-c-f91ee4af44ccdf02cefb
Status: RUNNING
Type: container
Architecture: x86_64
PID: 271236
Created: 2025/03/10 13:49 CET
Last Used: 2025/03/10 13:49 CET
Resources:
Processes: 7
Disk usage:
root: 673.00KiB
CPU usage:
CPU usage (in seconds): 1
Memory usage:
Memory (current): 32.58MiB
Network usage:
eth0:
Type: broadcast
State: UP
Host interface: vetha50804ab
MAC address: 00:16:3e:24:ae:e6
MTU: 1500
Bytes received: 20.93kB
Bytes sent: 20.32kB
Packets received: 150
Packets sent: 200
IP addresses:
inet6: fd42:7f0:dca8:1282:216:3eff:fe24:aee6/64 (global)
inet6: fe80::216:3eff:fe24:aee6/64 (link)
lo:
Type: loopback
State: UP
MTU: 65536
Bytes received: 3.46kB
Bytes sent: 3.46kB
Packets received: 48
Packets sent: 48
IP addresses:
inet: 127.0.0.1/8 (local)
inet6: ::1/128 (local)
Since you can reproduce this with just LXD and it’s not one of the common causes (Docker/iptables, firewall, proxy, vpn), you may need to reach out to the LXD team for advice.
Followed up as suggested in craft_providers.lxd.errors.LXDError: Timed out waiting for networking to be ready - Support - Ubuntu Community Hub.
With further help from the LXD folks in the previously linked question, it turned out I did have a Firewall (shame on me for saying the opposite!) and what solved my issue was apt remove firewalld
.