[LXD 4.1] Reset LXD init

Hello.

I unsucessfuly tried to reset lxd after making an error on the lxd init process. How can I do that ?

What do you want changed?

lxd init is only a convenient way to do a bunch of commands at once:

  • lxc config set
  • lxc network create
  • lxc storage create
  • lxc profile device add

So it’s often far easier to undo and reconfigure the bits you need than wipe everything clean and run init again.

Oh cool. I have an issue at this time with my first container tested. I doesn’t have an IPv4 and just an IPv6…
But It is my first test an I think is probably due to a bad typo filled during the lxd init.

Thanks for this anwser. I going to check that. :slight_smile:

lxc network show lxdbr0

Also, can you show:

  • ps fauxww
  • iptables -L -n -v

If I had to guess, your lxd init went fine but you have docker or firewalld messing with your firewall blocking DHCP from your container.

the ps fauxww and iptables command will be from the container or from the host ?

From the host.

https://pasteall.org/nUrj

Better like this:
https://pasteall.org/nUrj/raw

Is that Fedora 32?

Yes it is. The installation is from the lxd snap

Ok, so I suspect firewalld is the issue here and it’s preventing traffic from the LXD containers, in this case your DHCP traffic.

We have a section on how to convince firewalld to play nice here:
https://linuxcontainers.org/lxd/docs/master/networks#how-to-let-firewalld-control-the-lxd’s-iptables-rules

Ok. Thanks I give you a feeback after testing that :+1:

I had seen the purposed article to fix firewalld issues. It is explain that the problem is because lxd daemon start before the firewall. But is it more better to fix that by forcing the daemon to start after the firewalld ?

The firewall service may get restarted at a later point and break LXD again, so its better to fix the rules themselves.

1 Like

Right. Thank you for this anwser. I had missed this posibility :man_facepalming: