![native access no compatible update found native access no compatible update found](https://alternative.me/media/512/efront-thumbnail-iu7i5z92gspuw3z8-c.png)
So maybe TeamCity is querying for the Docker information before Docker has finished starting up. I think the problem occurs when the TeamCity Server and Build Agent services are up and running before the Docker service. TeamCity Server, TeamCity Build Agent and Docker Engine all run as services. I don't know about this issue on Linux, but here's my experience and solution on Windows. I posted this on as well, but I see a number of posters here having the same issue. Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata I suppose new teamcity version try to set variables from docker info? No server info for older docker ~]$ docker -vĭocker version 1.7.1, build ~]$ docker infoĭata loop file: /var/lib/docker/devicemapper/devicemapper/data
![native access no compatible update found native access no compatible update found](https://venturebeat.com/wp-content/uploads/2019/05/NET-5.png)
I have the same issue after updated to 2019.1 (build 65998).Īn agent with docker version 18.09.2 still works.Īnother Centos 6 agent with older docker version 1.7.1 didn't work any more. I do have the complete diagnostics of that machine however, if that helps.Īnyway, it seems that reinstalling the docker desktop version does solve this problem. De docker version and build shown in the GUI are the same as on the machine that doesn't like to play nice.I can't run docker -version on that machine because the docker host isn't connected so that sucks. Just for kicks I uninstalled the docker engine on one of the machines that was borked and reinstalled it. Rebooting the machine delivers some information: Running docker info on an agent that doesn't work is tricky, I updated the docker engine and now it is borked. ID: SDEF:VNMZ:I7IK:SLOK:5XNU:XEUD:TTMI:LXVE:EVMJ:DOAS:5JTF:MVFN Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslogĬontainerd version: 9754871865f7fe2f4e74d43e2fc7ccd237edcbce Network: bridge host macvlan null overlay This is the docker info of the build agent that does work: