Docker使用Team City Agent编写DNS问题

时间:2017-09-02 12:26:56

标签: docker networking docker-compose teamcity-9.0

我有以下docker-compose.yml文件,其中包含Team City Server和Agent,我想使用Docker版本17.06.1-ce-win24(13025)在我的本地Win 10 dev机器上运行:

version: '3.1'

services:
  tc_server:
    image: jetbrains/teamcity-server:2017.1.2
    ports: 
      - 8111:8111
    volumes:
      - teamcity_server:/data/teamcity_server/datadir
      - teamcity_server_logs:/opt/teamcity/logs
  tc_agent:
    image: jetbrains/teamcity-agent:2017.1.2
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - teamcity_agent_conf:/data/teamcity_agent/conf
    environment:
      SERVER_URL: http://tc_server:8111
volumes:
  teamcity_server:
  teamcity_server_logs:
  teamcity_agent_conf: 

Team City Server和Agent启动但我无法在UI中看到任何未经授权的代理。

我检查了泊坞日志:

tc_agent_1   | [2017-09-02 10:47:27,548]   WARN - buildServer.AGENT.registration - Error while asking server for the communication protocols via URL http://tc_server:8111/app/agents/protocols. Will try all protocols: java.net.ConnectException: Connection refused Connection refused) (enable debug to see stacktrace)
tc_agent_1   | [2017-09-02 10:47:27,549]   INFO - buildServer.AGENT.registration - Trying to register on server using 'polling' protocol.
tc_agent_1   | [2017-09-02 10:47:27,570]   INFO - buildServer.AGENT.registration - Registration using 'polling' protocol failed: java.net.ConnectException: Connection refused (Connection refused) (enable debug to see stacktrace)
tc_agent_1   | [2017-09-02 10:47:27,570]   INFO - buildServer.AGENT.registration - Trying to register on server using 'xml-rpc' protocol.
tc_agent_1   | [2017-09-02 10:47:27,581]   INFO - buildServer.AGENT.registration - Registration using 'xml-rpc' protocol failed: java.net.ConnectException: Connection refused (Connection refused) (enable debug to see stacktrace)
tc_agent_1   | [2017-09-02 10:47:27,581]   WARN - buildServer.AGENT.registration - Error registering on the server via URL http://tc_server:8111. Will continue repeating connection attempts.

代理似乎无法连接到服务器,但运行此命令会显示代理容器可以从TC Server容器中解析和检索(与日志警告相矛盾):

docker-compose exec tc_agent curl http://tc_server:8111/app/agents/protocols
<list><string>polling</string></list>

我尝试从Docker-compose.yml文件中删除代理并使用Docker单独进行代理(tc_default是容器正在使用的网络):

docker run --rm --network tc_default -e SERVER_URL=http://tc_server:8111 jetbrains/teamcity-agent:2017.1.2

这给出了以前在日志中发现的相同错误。所以我使用了服务器的IP地址:

docker run --rm --network tc_default -e SERVER_URL=http://172.18.0.3:8111 jetbrains/teamcity-agent:2017.1.2

此工作,代理出现在Team City Unauthorized Agents列表中。

这是代理的DNS问题,还是我错误地使用了docker-compose网络?我希望尽可能将服务器和代理保存在一个Docker-compose文件中。

3 个答案:

答案 0 :(得分:1)

从您的服务名称中删除_表单,它应该可以使用。我最近在使用http://service_name:port时无法使用python中遇到过问题。但是使用http://servername:port工作

虽然许多图书馆和地方都有_,但它仍不适用于所有

答案 1 :(得分:0)

您的tc_server需要在代理之前启动。在tc_agent服务配置中添加以下内容,以确保启动顺序:

depends_on:
      - tc_server

答案 2 :(得分:0)

这是对我有用的

docker-compose.yml

version: '3.8'
# Define the services/containers to be run
services:
  teamcity: # name of the service 
    image: 'jetbrains/teamcity-server'
    container_name: 'tmserver' # name of the container
    restart: always
    ports: 
      - "8111:8111" # specify the teamcity port default is 8111
    volumes: # This will store the plugin setup config data.
      - teamcity_data:/data/teamcity_server/datadir # Host is location /var/lib/docker/volumes/USERNAME_teamcity_data
      - teamcity_data:/opt/teamcity/logs

  teamcityagent: # name of the service 
    image: 'jetbrains/teamcity-agent'
    container_name: 'tmagent' # name of the container
    restart: always
    volumes: # This will store the plugin setup config data. example: /var/lib/docker/volumes/developer_teamcity_agent_data/_data
      - teamcity_agent_data:/data/teamcity_agent/conf # Host location /var/lib/docker/volumes/USERNAME_teamcity_agent_data 
    depends_on: # tells the teamcity_server to start first before the agent 
      - teamcity
    environment:  # Set environment variables aka Server url
      - SERVER_URL=http://teamcity:8111/ # we use the name teamcity for the url so its a container to container connection

volumes:
  teamcity_data:
  teamcity_agent_data: