You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@yetus.apache.org by "Yetus QA (JIRA)" <ji...@apache.org> on 2019/02/03 21:50:00 UTC
[jira] [Commented] (YETUS-758) docker-cleanup doesn't always clean
[ https://issues.apache.org/jira/browse/YETUS-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16759552#comment-16759552 ]
Yetus QA commented on YETUS-758:
--------------------------------
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 25s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} shellcheck {color} | {color:green} 0m 2s{color} | {color:green} There were no new shellcheck issues. {color} |
| {color:green}+1{color} | {color:green} shelldocs {color} | {color:green} 0m 0s{color} | {color:green} There were no new shelldocs issues. {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m 0s{color} | {color:green} The patch has no whitespace issues. {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m 7s{color} | {color:green} The patch does not generate ASF License warnings. {color} |
| {color:black}{color} | {color:black} {color} | {color:black} 0m 45s{color} | {color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/PreCommit-YETUS-Build/932/artifact/patchprocess/Dockerfile |
| JIRA Issue | YETUS-758 |
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12957464/YETUS-758.00.patch |
| Optional Tests | dupname asflicense shellcheck shelldocs |
| uname | Linux afff98c51041 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | precommit/src/main/shell/personality/yetus.sh |
| git revision | master / bf88009 |
| maven | version: Apache Maven 3.3.9 |
| shellcheck | v0.4.6 |
| Max. process+thread count | 46 (vs. ulimit of 1000) |
| modules | C: precommit U: precommit |
| Console output | https://builds.apache.org/job/PreCommit-YETUS-Build/932/console |
| Powered by | Apache Yetus 0.10.0-SNAPSHOT http://yetus.apache.org |
This message was automatically generated.
> docker-cleanup doesn't always clean
> -----------------------------------
>
> Key: YETUS-758
> URL: https://issues.apache.org/jira/browse/YETUS-758
> Project: Yetus
> Issue Type: Bug
> Components: Test Patch
> Affects Versions: 0.9.0
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Priority: Minor
> Fix For: 0.10.0
>
> Attachments: YETUS-758.00.patch
>
>
> With the revamp of how images get referenced in YETUS-723, images with multiple tags aren't able to be removed. e.g.:
> {code}
> REPOSITORY TAG IMAGE ID CREATED SIZE
> trekawek/azurite 2.6.5-1 13e75c93709b 7 months ago 107MB
> trekawek/azurite latest 13e75c93709b 7 months ago 107MB
> Untagged images:
> Apache Yetus images:
> Other images:
> Attempting to remove docker image 13e75c93709b
> Error response from daemon: conflict: unable to delete 13e75c93709b (must be forced) - image is referenced in multiple repositories
> Attempting to remove docker image 13e75c93709b
> Error response from daemon: conflict: unable to delete 13e75c93709b (must be forced) - image is referenced in multiple repositories
> {code}
> Specifcally rmi'ing the tag works:
> {code}
> docker rmi trekawek/azurite:latest
> Untagged: trekawek/azurite:latest
> docker rmi trekawek/azurite:2.6.5-1
> Untagged: trekawek/azurite:2.6.5-1
> Untagged: trekawek/azurite@sha256:09c1a9001adc491c5f191621a2df48e3f972bf843efa74ae6d16895cb56662d4
> Deleted: sha256:13e75c93709b930512c199b06f822fb0c34ea1dd4114a01e6b00bfd089f78f86
> Deleted: sha256:cde08104cdc69031a71a613d539b91515db42146b3d595313ee6642b8b01458e
> Deleted: sha256:6e41e7ae95796df2058f02a2eed9545eaad6e5c91a46a2349541b24141eff2ba
> Deleted: sha256:256ac8f43742a4a0ee2e9466abfe094d3fed0fb3391603dd69a7fb628d974661
> Deleted: sha256:880baa76624cdc7319adb4a67fbfbc5561d152dbabd27519e036b23342a4ea62
> Deleted: sha256:82d0fc10abb1c78bf4240daec73360066ac1c6870c78839965fa623a94dfad60
> Deleted: sha256:8dd02e14f198348365e2e6b8db527536232addf4a5badc5c4b7bb60a8f9e97b1
> Deleted: sha256:59401466fb8d00bfd23d31b5da6c3ee01a885760b38ab489451dc730e4b4ef06
> Deleted: sha256:cd7100a72410606589a54b932cabd804a17f9ae5b42a1882bd56d263e02b6215
> {code}
> We probably need to re-add some of the 'remove by tag' code that was removed by 723. (Using --force is way too dangerous)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)