Hi @simos
When i use this instruction, the container name .lxd is ready in host but when go inside of container i can’t ping domain names like google.com
what should i do at this situation?
Hi @simos
When i use this instruction, the container name .lxd is ready in host but when go inside of container i can’t ping domain names like google.com
what should i do at this situation?
One way (that worked great for me) is to follow the very simple instructions at the top of this page: A way to resolve container.lxd from host, in all cases - you’ll need to undo anything you’ve done until now though.
Thank you @akarelas-pt
lxdbr0 address with reboot doesn’t change?
I don’t know, @alizowghi. But I’ve had this set-up on 2 PCs and it’s never changed on me.
@alizowghi,
It probably doesn’t change because if you type: lxc network show lxdbr0
you get this, which maybe implies that the IP address is part of the network’s configuration:
config:
ipv4.address: 10.100.12.34/24
ipv4.nat: "true"
ipv6.address: faaa:faa:7777:bbbb::1/64
ipv6.nat: "true"
description: ""
name: lxdbr0
type: bridge
used_by:
I tested your solution and till now is working very well.
I think that’s right.