Running TeamCity server on Windows and agent in Docker

Hello, I've been having trouble connecting the TeamCity agent to the server. Here's my setup: TeamCity server is running as a service on my Windows 10 laptop (running on 172.20.7.154:8111), and I have a Windows Container based on the teamcity-agent:2018.1.1 image. Unfortunately the image doesn't appear on the server's "Unauthorized" list at all, and the logs keep saying that it timed out. I have uploaded the server and agent logs for clarity on the uploads.services.jetbrains.com webpage (they're called teamcity-agent.log and teamcity-server.log, I am not quite sure if I'm using this right so apologies for any confusion, I can reupload if needed). I would really appreciate it if anyone has any ideas on how to solve the problem, as I've been struggling with this for a few days, and I cannot find any resources online on combining a local server with a docker agent.

Here's the command I use to run my container, "external" is the name of a transparent network I've set up with Hyper-V:

docker run --rm -it --name teamcity-agent -v C:/ProgramData/TeamCity/agent/conf:C:/BuildAgent/conf -v C:/ProgramData/TeamCity/agent/logs:C:/BuildAgent/logs -e SERVER_URL="172.20.7.154:8111" -e AGENT_NAME="ContainerAgent" --network=external jetbrains/teamcity-agent:2018.1.1

My computer and the agent can both ping each other, so I think the network's setup correctly. As you can see I am able to ping the server IP when I execute powershell inside the container:

PS C:\> ping host.docker.internal

Pinging host.docker.internal [172.20.7.154] with 32 bytes of data:
Reply from 172.20.7.154: bytes=32 time<1ms TTL=128
Reply from 172.20.7.154: bytes=32 time<1ms TTL=128
Reply from 172.20.7.154: bytes=32 time<1ms TTL=128
Reply from 172.20.7.154: bytes=32 time<1ms TTL=128

Ping statistics for 172.20.7.154:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
PS C:\> ping 172.20.7.154

Pinging 172.20.7.154 with 32 bytes of data:
Reply from 172.20.7.154: bytes=32 time<1ms TTL=128
Reply from 172.20.7.154: bytes=32 time<1ms TTL=128
Reply from 172.20.7.154: bytes=32 time=1ms TTL=128
Reply from 172.20.7.154: bytes=32 time<1ms TTL=128

Ping statistics for 172.20.7.154:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms

However when I try to manually send an HTTP request to the TeamCity server, it times out, and I think this is also what happens to the running agent when it tries to connect:

PS C:\> iwr 172.20.7.154:8111
iwr : An error occurred while sending the request.
At line:1 char:1
+ iwr 172.20.7.154:8111
+ ~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (Method: GET, Re...1.14393.1000}:HttpRequestMessage) [Invoke-WebRequest], HttpRequestException
    + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

On another note, when I try to iwr <agent-ip>:9090 from my computer, this is what pops up in the agent logs:

[2018-08-28 14:47:51,817]   WARN -    jetbrains.buildServer.AGENT - Rejecting xml-rpc connection from /172.20.7.154
[2018-08-28 14:47:51,832]  DEBUG -    jetbrains.buildServer.AGENT - Rejecting xml-rpc connection from /172.20.7.154

I have also opened the port 8111 on my laptop's firewall for all inbound connections but that doesn't seem to help

PS C:\> netsh advfirewall firewall show rule name="Open Port 8111"

Rule Name:                            Open Port 8111
----------------------------------------------------------------------
Enabled:                              Yes
Direction:                            In
Profiles:                             Domain,Private,Public
Grouping:
LocalIP:                              Any
RemoteIP:                             Any
Protocol:                             TCP
LocalPort:                            8111
RemotePort:                           Any
Edge traversal:                       No
Action:                               Allow
Ok.

Not sure what is the source of the problem here. Just to clarify I have also tried doing this using the default nat network instead of a transparent one (including mapping the container port 9090 to localhost:9090) but it's pretty much exactly the same with the exception that pinging the server from within the agent sometimes fails.

If you need more information please let me know and I'll try to provide them.