[
https://issues.apache.org/jira/browse/BEAM-11263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17251891#comment-17251891
]
Beam JIRA Bot commented on BEAM-11263:
--------------------------------------
This issue is assigned but has not received an update in 30 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> Docker unable to remove container image because container is running
> --------------------------------------------------------------------
>
> Key: BEAM-11263
> URL: https://issues.apache.org/jira/browse/BEAM-11263
> Project: Beam
> Issue Type: Improvement
> Components: build-system, sdk-java-core, test-failures, testing
> Reporter: Tyson Hamilton
> Assignee: Tyson Hamilton
> Priority: P2
> Labels: Clarified, Done, stale-assigned
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Sometimes Jenkins jobs fail to cleanup the container images because the
> container is not yet shutdown. The failure looks like this,
>
> {code:java}
> 14:41:52 Error response from daemon: conflict: unable to remove repository
> reference
> "us.gcr.io/apache-beam-testing/java-postcommit-it/java:20201113182944" (must
> force) - container c28427d037c9 is using its referenced image 55ebc4bc6c8c
> {code}
> Adding the `–force` flag to the rmi command should resolve the issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
