Unmet requirements: docker.server.osType contains linux

Hi,

I have a Linux (Ubu 18.04) based TC installation with 2018.2.4 (build 61678).

docker and docker-compose is installed locally:

root@sd7:~# docker -v
Docker version 18.09.2, build 6247962
root@sd7:~# docker-compose -v
docker-compose version 1.17.1, build unknown

On the agent I see the following variables:

docker.version  18.09.2
dockerCompose.version  1.17.1

Thus, the agent is uncompatible / unmet:

Unmet requirements:
docker.server.osType contains linux
 
I can't understand this, other related posts are not identical / because of other issues.
 
Thanks for help,
Matthias
0
7 comments

Hi,

 

the issue with "docker.server.osType" not showing up usually means that the docker command run from the agent cannot connect with the docker daemon running. This is usually due to a lack of permissions, as docker by default only allows connections from root and users of the group docker: https://docs.docker.com/install/linux/linux-postinstall/

 

Please make sure to set the appropriate configuration (the user running the build agent is a member of the dockergroup). Then, restart the agent. That should make it work. If it doesn't you might need to restart the session to ensure that the group changes take effect.

1

Thanks, that was it!

(P.S.: Didn't find any TC docu about all these nasty prerequisites for docker support, e.g. also how to configure the best way things like registry logins etc.).

0

I've added a comment to document it in an issue we had here about it: https://youtrack.jetbrains.net/issue/TW-52609 to try and improve our documentation about it.

0
Default Agent-1
Unmet requirements:
docker.server.version exists
 
 I am not able to run build through an agent instead of that it goes under the build queue
0

Hi Dushant,

 

first of all, please don't post in multiple posts with a different question. It creates extra workload for us and it's not going to speed up any response.

 

Secondly, the likely answer to your problem is the first answer I provided in this same thread, and is very likely actually related to your docker installation and not to teamcity in itself. Please test it out.

0

We have many different teamcity servers running and have seen this error occur in two instances which is a small percentage of instances and it does not appear to be deterministic. The most recent occurrence was resolved by manually starting an agent and that somehow resulted in many other agents being created and builds running. No configuration was changed for the build agents.

0
Hi Cameron,

Could you provide more details on the behavior you encountered? I will see if it is related or not.
In general, such issues are related to the Docker configuration, as Denis mentioned, and should be resolved by following the recommendations he provided.

Best regards,
Anton
0

Please sign in to leave a comment.