Spec: Jammy jelly fish and lxd 5.10/stable.
Juju bootstrapping failed ‘waiting for address’. I have an assumption that it is a network error. It seems like there is no IPV4 assignment for the container I newly created.
I tried to use lxd 5.0/stable and encountered a similar issue.
I also launched an Ubuntu container, which doesn’t have an IP address assigned to it.
Appreciate your help
Are there are any issues with lxd and encrypted disks? I have a newly installed Jammy and the only set up I have is that my Secure Boot is disabled
When I launched, the containers don’t get a network address. Unclear why at this point. On jammy with 5.0/stable and 5.10/stable. The default profile has eth0.
What does “ip a” and “ip r” show inside container and on host?
Are you running latest juju?
Do you have docker installed on the host?
Also please show “lxc network ls” and the “lxc network show (network)” for the network in question.
Set up 1:
Juju version: 2.9.38-ubuntu-amd64
Ubuntu: 22.04
LXD: 5.10/stable
X Failed to Bootstrap Juju
Set up 2:
Juju version: 2.9.38-ubuntu-amd64
Ubuntu: 22.04
LXD: 5.0/stable
X Failed to Bootstrap Juju
Set up 3:
Juju version: 2.9.38-ubuntu-amd64
Ubuntu: 22.04
LXD: 4.0/stable
X Failed to Bootstrap Juju
Solution tried:
To allow traffic from lxdbr0 interface to the LXD host and for traffic from lxdbr0 to be routed to the external network without allowing all external inbound traffic:
sudo ufw allow in on lxdbr0
sudo ufw route allow in on lxdbr0
sudo ufw route allow out on lxdbr0
Try different LXD versions
Failed
My machine is encrypted, and secure boot is disabled. Will it impact any of the installation?
Possible reason for failure:
When I launch LXD - e.g. ubuntu 22.04 or Juju, the containers don’t get a network address. Unclear why at this point. On jammy with 5.0/stable and 5.10/stable. The default profile has eth0.
This set up worked with me when I tried to install Juju in my 20.04. Is this because of the OS version?
Other bugs related:
Does launching a container manually work?
I.e lxc launch images:ubuntu/jammy c1 -n lxdbr0
What does “lxc warning list” show?
Also can you show output of “sudo ss -ulnp” on the host
Please also show “lxc network show lxdbr0”
Ah the dhcp server seems to be disabled.
Please try doing
lxc network set lxdbr0 ipv4.dhcp=true
And then restart or recreate the instance.
Hi Thomas I enabled dhcp
lxc info c4
Name: c4
Location: none
Remote: unix://
Architecture: x86_64
Created: 2023/02/02 13:17 CET
Status: Running
Type: container
Profiles: default
Pid: 8283
Ips:
eth0: inet6 fe80::216:3eff:fe02:51ff vethc2fe8871
lo: inet 127.0.0.1
lo: inet6 ::1
Resources:
Processes: 13
CPU usage:
CPU usage (in seconds): 0
Memory usage:
Memory (current): 40.23MB
Network usage:
eth0:
Bytes received: 174B
Bytes sent: 3.17kB
Packets received: 2
Packets sent: 19
lo:
Bytes received: 0B
Bytes sent: 0B
Packets received: 0
Packets sent: 0
What does sudo ss -ulpn show now, with ipv4.dhcp=true set I would expect to see this line:
UNCONN 0 0 0.0.0.0%lxdbr0:67 0.0.0.0:* users:(("dnsmasq",pid=5264,fd=4))
Also does running dhclient inside the container get you an IP?