[
https://issues.apache.org/jira/browse/BEAM-11263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17290101#comment-17290101
]
Beam JIRA Bot commented on BEAM-11263:
--------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> 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
> Priority: P2
> Labels: Clarified, Done, stale-P2
> 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)
