Tom Morello

After switching this time, it allowed me to assign the IP. I am not sure what happened, but now it's working with the assigned IP, as well as with the VLAN and containers. Thank you very much

Thanks, it definitely helped. I also tried restoring the original docker.img with the proper ipvlan configuration, and it's working fine now. Let me ask you a question, though. I forgot that I switched to macvlan after the 6.12.6 update because ipvlan was not allowing me to assign an IP to the container. For example, my Time Machine container previously had the 192.168.1.220 IP assigned, but now it's just acting as a bridge without an assigned IP. Do you know how can i fix that ?

I've started to have a few incidents where my unraid server just dies and i have to manually reboot it. The GUI dies or the SSH stops responding randomly. But since thursday, I am unable to use my docker containers. I've tried deleting the docker.img without luck so i'll be restoring it once it's back online. I've also tried to turn off vms & docker without luck, it's still starting them. Here are the diagnostics Not sure what to do, but the GUI is not stable at all, ass it just stops to respond whenever i tried to use it, also, parity is okay as far as i know. Thanks ! logs.zip

I am currently trying to setup a test environment for some apps. My plan is to publish from my local device to ACS (Azure Container Registry) and then have it updated on UnRAID. So far, i was able to setup an SPN to then login and get the image using Docker's UI. The problem comes while updating. I've been pushing some images to the ACS, but i can't force it to update. Any idea of what can i be doing wrong ? Edit: Doing a manual docker pull updates the image. Still not showing on the UI.