You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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?
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.The text was updated successfully, but these errors were encountered: