Steven Hartland

Thanks for your thoughts @jeremyg484, can anyone think of a situation which `HostAccessPorts` can handle which the DNS route can't?

Thanks for all the extra info. I wonder what the expected behaviour should be. Could you confirm what the name resolves to?

Oh to confirm my test host was Windows under WSL. So would be interested to understand that OSs work and what doesn't

Tested on Mac and it also works fine.

> Actually, given this a tiny bit more thought, I'm not sure my additional suggested changes to `HostAccessPorts` really make sense as this would only be a problem for servers...

That's what I see too, Linux seems to be the odd one out.

> 1. `docker run --rm -it --add-host host.docker.internal:host-gateway alpine cat /etc/hosts` so we can see if it's getting set to the docker0 gateway address like it does on Linux ```shell...

It's odd that it specifically has loading stats but doesn't populate them, will have a look at the code.

It seems wasteful to have to specify both as they would be identical, so could there be an option to relax this so that either is valid?

Yer looks like an edge case, but definitely think it would be good to use the schema description if not overridden to avoid replicating strings unnecessarily, as duplicate strings also...