Windows Docker containers
Currently, they do not support Since Windows 10 version 1803 with KB4340917 it's possible to use port mapping from containers to localhost, so the
-poption does not have any effect for localhost. However, . For previous Windows versions it works for the non-localhost IP address associated with this machine and you can access a running application via the machine's hostname or determine the IP address via the
ipconfigcommand. Note that the
netstat -ancommand may not show that the port is open on any IP address, while in fact it can work. This is also a known problem of Docker on Windows.
On Windows 10, the memory allocated per container is 1GB by default. To increase this value, use the following memory options:
docker run ... -m 2GB -e TEAMCITY_SERVER_MEM_OPTS="-Xmx2g -XX:ReservedCodeCacheSize=350m"
When starting a TeamCity server from a Windows Docker image, make sure to grant
Authenticated UsersFull control over the directories used as volumes. See the related issue.
- When starting a Windows Docker container with the directory C:/BuildAgent/work mapped as a volume to the container host, Git for Windows fails with a following error:
Invalid path '/ContainerMappedDirectories': No such file or directory". The workaround is not to add "C:/BuildAgent/work" as a volume.