I installed some containers that needed to talk with the rest of the servers outside of the container and found it weird they couldn't resolve at all over DNS. 
Turns out that there are few things you need to configure for it to work properly.

1. Make sure you have DNS resolving configured on the host and pointing to your DNS servers
   • You can check the resolver file on a container by using this command: sudo docker exec <container> cat /etc/resolv.conf
   • To test if the container can resolve a DNS name use this command: sudo docker exec <container> ping <DNSname> 
2. Check the assigned docker network for the container, if it's in a different network it might not be able to resolve using DNS
   • To check how many networks there are use this command: sudo docker network ls
   • To find out which network the container is using, use this command: sudo docker inspect <container> -f "{{json .Networksettings.Networks }}"
     You should see the name of the network in the results
   • To remove the network from the container use this command: sudo docker network disconnect <networkname> <container> 
   • To add a network to the container use this command: sudo docker network connect <networkname> <container>
     You might need to restart the container before the DNS works

In older versions of Windows 11 en Windows 10 you could simply extract the layout and deploy in the default users folder, but this has changed in the newer versions of Windows. 
You now need to deploy two seperate files, one for the start menu and one for the taskbar for it all to work now. 
The way you deploy it is up to you, can be inside an image you sysprep, MDT or Intune, everything works!

It's been a while since I did this and I never documented it for myself. So here it is and for anyone else that comes across this.

It's widely known by know that KB5028997 is causing issues with it failing. This is because this patch requires a larger WinRE partition and by default this is 500 MB.
To get over this hurdle, you need to increase the size and luckily the server does not need a reboot or be shutdown to perform this.