如果不从交互式终端运行,Python subprocess.communicate无法捕获来自runc容器的输出

时间:2019-03-11 14:05:17

标签: python subprocess runc

我有一个运行子进程并捕获输出的脚本,但是仅当我在交互式外壳中运行它时该脚本才起作用,但是如果是从Jenkins运行则不起作用。

tst_subscriber = ["timeout", "-s", "KILL", str(timeout),"bash","-c", subsciber_executable]
tst_publisher = ["timeout","-s", "KILL", str(timeout),"bash","-c", publisher_executable]
kill_publisher = lambda process: subprocess.call(['docker-runc', 'delete', pub_name, "-f"])
kill_subscriber = lambda process: subprocess.call(['docker-runc', 'delete', sub_name, "-f"])

test_env = os.environ.copy()
# workaround for buffering problem which causes no captured output for python subprocesses
test_env["PYTHONUNBUFFERED"] = "1"

sub_pro = Popen(tst_subscriber, stdout=subprocess.PIPE, env=test_env)
pub_pro = Popen(tst_publisher, stdout=subprocess.PIPE, env=test_env)

timeout_sub = Timer(timeout, kill_subscriber, [sub_pro])
timeout_pub = Timer(timeout, kill_publisher, [pub_pro])

timeout_sub.start()
timeout_pub.start()
(output, err) = sub_pro.communicate()

print "Subscriber stdout:"
print output
print "Subscriber stderr:"
print err

1 个答案:

答案 0 :(得分:0)

由于几个开放的runc问题#1965 #1721,在config.json中设置terminal: true会导致管道困难。看到terminal: false解决了这个问题。