-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No signature for postgres:11.11-alpine, postgres:12.6-alpine or postgres:13.2-alpine #822
Comments
As noted in docker-library/official-images#1516, it's unfortunately been broken for quite some time now. 😞 If you check the timestamp on the images with "valid signatures" I think you'll see that they're horrifyingly outdated (which is a pretty, uh, interesting failure mode, to say the least 😬). (Closing this one, since there's not really anything we can do at this level.) |
Looks like it was working 3 months ago so I wouldn't say it's way outdated (they are 3 months old). Basically all the versions after that don't have it though. postgres 11.10-alpine f61df677592b 3 months ago 156MB |
Also as another note I checked in our ansible code and I've been checking for signatures on postgres images since march 2017 and upgrading postgres every 3-6 months and it always worked prior, so seems like a recent change for sure |
History of all signed images: `notary -s https://notary.docker.io list docker.io/library/postgres 10 d59da2a8b1731cbcd713ac9747d7b48bbfcc88fabea4ed66670f907b75dee5b8 1215 targets |
$ export DOCKER_CONTENT_TRUST=1
$ docker pull postgres:11.11-alpine
No valid trust data for 11.11-alpine
One prior versions postgres:11.10-alpine, postgres:12.5-alpine or postgres:13.1-alpine all have valid notary signatures
The text was updated successfully, but these errors were encountered: