[ 
https://issues.apache.org/jira/browse/BEAM-4051?focusedWorklogId=90106&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-90106
 ]

ASF GitHub Bot logged work on BEAM-4051:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 11/Apr/18 18:41
            Start Date: 11/Apr/18 18:41
    Worklog Time Spent: 10m 
      Work Description: udim commented on issue #5100: [BEAM-4051] Clean up 
docker networks generated by hdfs integration tests.
URL: https://github.com/apache/beam/pull/5100#issuecomment-380555021
 
 
   run python postcommit

----------------------------------------------------------------
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:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 90106)
    Time Spent: 0.5h  (was: 20m)

> python postcommit failure in docker-compose
> -------------------------------------------
>
>                 Key: BEAM-4051
>                 URL: https://issues.apache.org/jira/browse/BEAM-4051
>             Project: Beam
>          Issue Type: Bug
>          Components: testing
>            Reporter: Udi Meiri
>            Assignee: Udi Meiri
>            Priority: Major
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> [https://builds.apache.org/job/beam_PostCommit_Python_Verify/4661/consoleText]
> Error is:
> Creating network 
> "hdfs_it-jenkins-beam_postcommit_python_verify-4661_test_net" with the 
> default driver
> could not find an available, non-overlapping IPv4 address pool among the 
> defaults to assign to the network
>  
> I assume that the issue is that the networks being created are not being 
> cleaned up.
> Looking briefly online the solution seems to be something like "docker 
> network prune --force".



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to