docker - Buildmaster 不监听端口

标签 docker tcp docker-compose protocol-buffers buildbot

我正在尝试从我计算机上的 docker-compose 文件运行 Buildbot,使用 Buildbot 提供的 buildmaster 和 worker 的图像。我将buildmaster端口定义为9989,并且在我的master.cfg中我定义了一个监听9989端口的PBChangeSource。但是,似乎在我运行docker-compose up之后,没有进程监听在端口 9989(运行 lsof -nP -iTCP:9989 | grep LISTEN 之后)。这似乎得到了以下事实的进一步支持:当我运行 buildbot sendchange -m my.0.0.ip:9989 -a Jimmy:secret -W buildbot 时,扭曲的服务器超时,就像它一样如果我使用不同的端口运行相同的命令,例如buildbot sendchange -m my.0.0.ip:5000 -a Jimmy:secret -W buildbot。有谁知道如何让 PB 监听变化?谢谢!

这是我的 master.cfg:

# -*- python -*-
# ex: set filetype=python:

import os

from buildbot.plugins import *

# This is a sample buildmaster config file. It must be installed as
# 'master.cfg' in your buildmaster's base directory.

# This is the dictionary that the buildmaster pays attention to. We also use
# a shorter alias to save typing.
c = BuildmasterConfig = {}

####### WORKERS

# The 'workers' list defines the set of recognized workers. Each element is
# a Worker object, specifying a unique worker name and password.  The same
# worker name and password must be configured on the worker.

c['workers'] = [worker.Worker("example-worker", 'pass')]

if 'BUILDBOT_MQ_URL' in os.environ:
    c['mq'] = {
        'type' : 'wamp',
        'router_url': os.environ['BUILDBOT_MQ_URL'],
        'realm': os.environ.get('BUILDBOT_MQ_REALM', 'buildbot').decode('utf-8'),
        'debug' : 'BUILDBOT_MQ_DEBUG' in os.environ,
        'debug_websockets' : 'BUILDBOT_MQ_DEBUG' in os.environ,
        'debug_lowlevel' : 'BUILDBOT_MQ_DEBUG' in os.environ,
    }
# 'protocols' contains information about protocols which master will use for
# communicating with workers. You must define at least 'port' option that workers
# could connect to your master with this protocol.
# 'port' must match the value configured into the workers (with their
# --master option)
c['protocols'] = {'pb': {'port': os.environ.get("BUILDBOT_WORKER_PORT",9989)}}

####### CHANGESOURCES

# the 'change_source' setting tells the buildmaster how it should find out
# about source code changes.  Here we point to the buildbot clone of pyflakes.

c['change_source'] = changes.PBChangeSource(port=9989 , user = 'Jimmy' , passwd = 'secret')

####### SCHEDULERS

# Configure the Schedulers, which decide how to react to incoming changes.  In this
# case, just kick off a 'runtests' build

c['schedulers'] = []
c['schedulers'].append(schedulers.SingleBranchScheduler(
                            name="all",
                            change_filter=util.ChangeFilter(branch='master'),
                            treeStableTimer=None,
                            builderNames=["runtests"]))
c['schedulers'].append(schedulers.ForceScheduler(
                            name="force",
                            builderNames=["runtests"]))

####### BUILDERS

# The 'builders' list defines the Builders, which tell Buildbot how to perform a build:
# what steps, and which workers can execute them.  Note that any particular build will
# only take place on one worker.
factory = util.BuildFactory()
# check out the source
# run the tests (note that this will require that 'trial' is installed)
factory.addStep(steps.ShellCommand(command=["ls" , ".."]))
c['builders'] = []
c['builders'].append(
    util.BuilderConfig(name="runtests",
      workernames=["example-worker"],
      factory=factory))

####### STATUS TARGETS

# 'status' is a list of Status Targets. The results of each build will be
# pushed to these targets. buildbot/status/*.py has a variety to choose from,
# like IRC bots.

c['status'] = []

####### PROJECT IDENTITY

# the 'title' string will appear at the top of this buildbot installation's
# home pages (linked to the 'titleURL').

c['title'] = "dummy"
c['titleURL'] = "https://github.com/jimmykim1/dummy"

# the 'buildbotURL' string should point to the location where the buildbot's
# internal web server is visible. This typically uses the port number set in
# the 'www' entry below, but with an externally-visible host name which the
# buildbot cannot figure out without some help.

c['buildbotURL'] = os.environ.get("BUILDBOT_WEB_URL", "http://localhost:8010/")

# minimalistic config to activate new web UI
c['www'] = dict(port=os.environ.get("BUILDBOT_WEB_PORT", 8010),
                plugins=dict(waterfall_view={}, console_view={}))
c['www']['change_hook_dialects'] = {
        'github' : {
            'secret' : 'himitsu',
            'strict' : False,
        }
}

####### DB URL

c['db'] = {
    # This specifies what database buildbot uses to store its state.  You can leave
    # this at its default for all but the largest installations.
    'db_url' : os.environ.get("BUILDBOT_DB_URL", "sqlite://").format(**os.environ),
}

最佳答案

问题与我的 docker-compose.yml 的配置有关。我必须在 ports 下为我的 buildmaster 列出“9989:9989”。现在建筑大师正在倾听。

关于docker - Buildmaster 不监听端口,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/51506073/

相关文章:

r - 如何部署一个写入日志文件的 Plumber docker?

Docker:找不到 Alpine linux 社区包

java - 使用java编程的modbus协议(protocol)问题

windows - Windows位置上的Docker根文件夹

django - 在docker-compose break run中使用network_mode ='host':主机类型网络不能与链接一起使用

docker - 在docker容器内删除的文件没有释放空间

docker - 通过共享网络连接docker-compose文件

ubuntu - ubuntu 的 .pac 文件 - 命令行

java - TCP 文件传输问题

macos - 听 TCP 127.0.4.1 :2040: bind: can't assign requested address