The e2e failure is unrelated, but looks like a genuine failure with the v29.9.0-rc.1 daemon; at a quick glance, it's either a race, or a bugfix that caused the output to change (need to check), combined with a test that may be too strict;
=== Failed
=== FAIL: e2e/container TestRunAttachedFromRemoteImageAndRemove (1.33s)
run_test.go:42: assertion failed:
--- expected
+++ actual
@@ -1,4 +1,5 @@
Unable to find image 'registry:5000/alpine:test-run-pulls' locally
test-run-pulls: Pulling from alpine
+63b65145d645: Pulling fs layer
Digest: sha256:e2e16842c9b54d985bf1ef9242a313f36b856181f188de21313820e177002501
Status: Downloaded newer image for registry:5000/alpine:test-run-pulls
You can run 'go test . -update' to automatically update testdata/run-attached-from-remote-and-remove.golden to the new expected value.'
Originally posted by @thaJeztah in #7351 (comment)
The e2e failure is unrelated, but looks like a genuine failure with the v29.9.0-rc.1 daemon; at a quick glance, it's either a race, or a bugfix that caused the output to change (need to check), combined with a test that may be too strict;
Originally posted by @thaJeztah in #7351 (comment)