[
https://issues.apache.org/jira/browse/BEAM-6699?focusedWorklogId=200172&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-200172
]
ASF GitHub Bot logged work on BEAM-6699:
----------------------------------------
Author: ASF GitHub Bot
Created on: 18/Feb/19 18:13
Start Date: 18/Feb/19 18:13
Worklog Time Spent: 10m
Work Description: ryan-williams commented on issue #7870: [BEAM-6699]
Configure artifact server port in DockerizedJobContainer
URL: https://github.com/apache/beam/pull/7870#issuecomment-464832627
Thanks for the quick fix @mxm, this lgtm (though I don't have great context
on these code-paths).
Any idea why this suddenly broke? Do you think it's due to recent Docker
upgrades?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 200172)
Time Spent: 0.5h (was: 20m)
> Docker iptables command fails while running
> :beam-sdks-python:portableWordCountBatch
> ------------------------------------------------------------------------------------
>
> Key: BEAM-6699
> URL: https://issues.apache.org/jira/browse/BEAM-6699
> Project: Beam
> Issue Type: Bug
> Components: runner-flink
> Reporter: Ryan Williams
> Assignee: Maximilian Michels
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Attempting to run portable python wordcount*:
> {code:java}
> ./gradlew :beam-sdks-python:portableWordCountBatch{code}
> fails:
> {code:java}
> > Task :beam-sdks-python:portableWordCountBatch
> INFO:root:Using latest locally built Python SDK docker image.
> INFO:root:==================== <function lift_combiners at 0x11951a578>
> ====================
> docker: Error response from daemon: driver failed programming external
> connectivity on endpoint angry_lamarr
> (d7b5f6f6cafc143ed4a5f37e32e6fcb0d04fe0ebb67c50d544482bbbe3bf6ee5): (iptables
> failed: iptables --wait -t nat -A DOCKER -p tcp -d 0/0 --dport 32777 -j DNAT
> --to-destination 172.17.0.2:0 ! -i docker0: iptables v1.6.2: Port `0' not
> valid
> Try `iptables -h' or 'iptables --help' for more information.
> (exit status 2)).
> time="2019-02-17T04:26:10Z" level=error msg="error waiting for container:
> context canceled"{code}
> [~mxm] thinks it might be a docker-on-mac problem. I recently updated Docker
> on this macbook to version 2.0.0.3 (31259), and I'm testing from current
> {{HEAD}},
> [cdea885872|https://github.com/apache/beam/commit/cdea885872b3be7de9ba22f22700be89f7d53766].
> I don't see where that invalid {{iptables}} command is being generated.
> [Various|https://github.com/jupyterhub/jupyterhub/issues/1565]
> [other|https://github.com/whisklabs/docker-it-scala/issues/18]
> [issues|https://github.com/ansible/ansible/issues/21091]
> [mention|http://www.programmersought.com/article/3145360553/] that error
> ("{{Port `0' not valid}}"), but I don't see any info about how to debug.
> * Building the job-server container before running seems to complete
> successfully and be picked up by the wordcount task:
> {code:java}
> ./gradlew -p runners/flink/job-server-container docker{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
