Ablatem

I was able to restore a 'test' vm which looks fine.

I created a new vm and used the same name as before as assigned CPU and RAM. The Primary vDisk location is set to Auto since it was using a valid path - /mnt/user/domains/RedHat/vdisk1.img

Network Source is virbrO
Network Model is virtio-net
 
I didn't make any other changes. So far so good - I will take another look at it and then try a restore of another VM.

Does this sounds like the correct process to use as far as recreating the vm's?

Note: I had to change the Network Source to br0  - Network Model - left this the same - virtio-net
This change gave me network connectivity.  I will use this setting going forward.

I ended up updating the 'Folders' app and use 'FolderView' instead. 

I also updated to 6.12.6 which didn't affect the docker issue.
 
Once I installed FolderView, I was able to mange the containers 'normally'. I could start, stop and pause and I can also create folders once again so I can organize my containers.

I was able to test this on a Windows 2016 server that had the same issue. I generated a mac address and then made the network changes:


 
I was able to Update this with no problem.  I checked the Device Manager on the vm and the network connection was there and working fine!
 
Thanks for your help!!!
 
Rick