Fix dangling filter for images command#1201
Fix dangling filter for images command#1201TomSweeneyRedHat wants to merge 1 commit intocontainers:masterfrom
Conversation
|
LGTM |
|
Looks like your tests are failing. |
|
@rhatdan yeah, they passed locally in my sandbox, trying to figure out what's different in Travis CI. |
Signed-off-by: TomSweeneyRedHat <tsweeney@redhat.com>
0b57db3 to
aaac18e
Compare
|
bot, retest this please |
|
bot, retest this please. |
|
LGTM |
|
I'm going to close and then reopen in hopes that will get Red Hat CI hip. |
|
📌 Commit aaac18e has been approved by |
|
☀️ Test successful - status-papr, status-travis |
|
@umohnani8 I believe the intermediate images that you're describing, if tagged as ":" are also considered to be dangling. But I'd take @nalind 's or @rhatdan 's word on that over mine. |
|
I would have to check if Docker considers them dangling. That would be the standard I guess. |
Signed-off-by: TomSweeneyRedHat <tsweeney@redhat.com> Closes: containers#1201 Approved by: rhatdan
Signed-off-by: TomSweeneyRedHat tsweeney@redhat.com
In version 1.4 of Buildah and earlier, the internal name for a dangling image was
<none>. With changes that came in after 1.4, the internal name was changed to<none>:<none>and this caused thebuildah images --filter dangling=truecommand to no longer work.Rather than comparing strictly to
<none>, this change does a strings.contains() for that. I've also added tests so if we fall off the rails again in the future, the test system will catch it.Addresses: #1199
Tests: