You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2021/03/10 17:19:02 UTC
[jira] [Commented] (BEAM-11263) Docker unable to remove container
image because container is running
[ https://issues.apache.org/jira/browse/BEAM-11263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17298983#comment-17298983 ]
Beam JIRA Bot commented on BEAM-11263:
--------------------------------------
This issue was marked "stale-P2" and has not received a public comment in 14 days. It is now automatically moved to P3. If you are still affected by it, you can comment and move it back to P2.
> 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: P3
> Labels: Clarified, Done
> 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)