search

JetBrains / teamcity-docker-agent

TeamCity agent docker image sources
https://hub.docker.com/r/jetbrains/teamcity-agent/
Apache License 2.0
77 stars 64 forks source link

Cannot connect to self-hosted docker registry (.local) #36

Open johnkors opened 6 years ago

johnkors commented 6 years ago

I'm having the same issue reported here – in that I cannot get the tc-agent to talk to a self-hosted docker registry found at myserver.local (i.e. a .local) address. It can fetch images from dockerhub, but not our internal registry.

According to this comment, there already should be a fix — but I'm not seeing it.

Is it only me?

Using jetbrains/teamcity-agent:latest on Ubuntu.

shanesiebken commented 5 years ago

I think that I am seeing this issue too. At least, that's the best that I can figure at this point. I'm using Docker-in-Docker (may god strike me dead) in a kubernetes cluster with an in-cluster registry, which is reached at the typical [...].svc.cluster.local, and docker fails to operate against it with a no such host error, even though an nslookup on the dind container shows the correct target IP.

kir commented 5 years ago

Hi, could you please make sure the problem is related to teamcity-agent image. For that, please start the teamcity-agent container, attach to it, and try connecting to the host machine. And compare with non-teamcity agent container - is there any difference?

If there is, please file a detailed bug report to https://youtrack.jetbrains.com/newIssue?project=TW&c=Assignee%20maxkir&c=Subsystem%20Docker

Thanks!