That’s it! After deleting the ip route after starting the instance I was able to lookup names again. However, what is adding the records when I start up the instance? When I restart the instance it adds the records back, again. Is this something within incus that adds the records?
I think that depends a bit on what kind of network type you have configured for your container. For example if you use a nictype ipvlan or routed you can disable the ipv4.gateway. All other types don’t have that option Container => devices => nic.
I am using a bridge.
I suppose this would likely be related to what I am experiencing.
So you messed up your network without knowing how to fix it. Well, at least post your settings, so other can try to figure out.
You said you use a bridge. Well, what bridge? linux bridge or ovs bridge? And I guess you use bridge to create a port for host, If so, post your host network setting.
And I have a feeling that you mix host bridge with incusbr0 which I don’t know how to solve.
And I guess you let container uses the same bridge as host. If so, post the container network setting too.
I can fix it, that’s not a problem. I was only literally following the documentation on how to initialize incus incus admin init. It created incusbr0 on its own as a network device on the default profile. I did not realize I had to do anything else to get things rolling, I did not add anything else to the physical networks. My environment is now back to how it was before adding the incus bridge. Looking at the post that someone else had made, it seems I should be creating a physical bridge on my environment, first.
1 Like
Okay, I figured it out. Interestingly enough, I tipped off by this post on proxmox. What I was experiencing is the same thing as the poster.
I am running LXQT, and I believe by default it decided to use connman instead of network-manager. Since everything I was seeing had to do with something adding different ip routes after starting, and the behavior of connman is different from network-manager (I never used the former till I installed Debian 12 w/ LXQT). Since moving to network-manager, serviced.networking is working correctly, too!
The solution, incus does not seem to behave properly with connman (or maybe the other way around). So do not use it!
Thank you, all, for your assistance. It makes sense why everything was so confusing.