[Fixed] jetbrains/teamcity-agent docker reports incompatible runner NuGet Installer

Answered
Avatar
Permanently deleted user
Created

I am trying to move a small scale test with a Teamcity windows install by the dev team to more permanent hosting using docker containers for both the server and its build agents..  I've had no major issues moving the server itself to the docker container on debian, but getting the build agent is giving me a lot more trouble...

All current projects are net462, with some newer ones targetting netcore3.1, but as I understand the windowsservercore-2004 image on which it is based should contain the necessary targets for building all projects currently defined.

The agent doesn't even get that far though... it reports all build configurations as incompatible, on the NuGet Installer no less... as i understand this should be pre-installed..?

Incompatible runner:     NuGet Installer
Unmet requirements:
Exists=>(DotNetFramework4\.(6\.(?!0)|[7-9]|[\d]{2,})[\d\.]*_.+) exists
Exists=>(DotNetFramework(4\.[5-9]{1}.*|[5-9]{1}.*|\d{2,}.*)_x86|Mono(3\.[2-9]{1}.*|3\.\d{2,}.*|[4-9]{1}.*|[\d]{2,}.*)) exists
MSBuildTools16.0_x86_Path exists
 
The original restore of TC was using NuGet 5.4.0, while the agent should have 5.8.0 pre-installed, so I tried upgrading the tool version to 5.8.0 in TC, but it makes no difference. I did notice that the agent reports something about requiring .Net framework during startup, i've highlighted it in the logs below.
 
Update: i found the cause, apparently docker was pulling an older image when i was using "jetbrains/teamcity-agent:latest".. it was getting an image based on 1903. Using "jetbrains/teamcity-agent:latest-windowsservercore" fixed it.

 

 

Votes

0

Share

1 comment
Avatar
Velkumar Santhanaraj
Created

I'm also facing same issue. 

I'm running Linux docker container. 

0

Please sign in to leave a comment.