Been having some networking issues off / on since before the 7.0 upgrade, but seems to be worse now. Originally i was having issues connecting to unraid connect, the CA wasn't working properly to detect updates. doing the unraid-api restart command seemed to resolve it sometimes or maybe for 5 minutes then back... my containers all still seemed to work fine and i didn't notice any problems with their connectivity. 

 

For the last week or so i've been having issues where the containers are unable to connect to internet. For the ones that have ping command available they show a name resolution error. When this came up last week i found some articles pointing to turn off enable host access to custom network, do a force update, try again. Some variation of that did work for me eventually. I believe the last thing i did was to set them to host networking, sping them up, they connected, set them back to my custom network IP and then start and they all just worked. until last night.... 

 

I've done similar steps today, turned off the enable host access to custom network and tried again. no change. set to host network for the container and they work fine, when i go back to my custom network and the designated ip they start up fine but don't connect. I've run this ipvlan network for 2-3 years now mostly without issue once i understood how ti worked, not sure what's going on now and how to troubleshoot next. 

 

I do run an unbound container to provide dns to my vlans but as part of the troubleshooting here i pointed all the vlans to just use automatic dns from my net provider and bypass my dns. 

 

diagnostics attached. suggestions appreciated. 

rlyeh-diagnostics-20250204-0742.zip

Open a terminal window and type

docker run hello-world

 

and post the results.

15 minutes ago, JorgeB said:

Open a terminal window and type

docker run hello-world

 

and post the results.

Hello from Docker!
This message shows that your installation appears to be working correctly.

To generate this message, Docker took the following steps:
 1. The Docker client contacted the Docker daemon.
 2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
    (amd64)
 3. The Docker daemon created a new container from that image which runs the
    executable that produces the output you are currently reading.
 4. The Docker daemon streamed that output to the Docker client, which sent it
    to your terminal.

To try something more ambitious, you can run an Ubuntu container with:
 $ docker run -it ubuntu bash

Share images, automate workflows, and more with a free Docker ID:
https://hub.docker.com/

For more examples and ideas, visit:
https://docs.docker.com/get-started/

That's working correctly, does a manual docker pull work for the containers that you cannot update using the GUI?

yes docker pull works, it's the application in that container that isn't getting out to the internet for some reason. if i set the container to host networking it works, when i set it to my customer ipvlan network ip it won't. ip's for each app on ipvlan network has been my setup for couple of years without any headaches or issues like i'm having now. 

Oh, sorry, misunderstood, cannot really help with that, but maybe someone else can.