Open macdjord opened 1 week ago
Just to be clear here: I'd really like to inspect the build cache metadata for the ADD https://ssl-config.mozilla.org/ffdhe2048.txt
layer of the existing image, so that I can check things like 'what ETag is it expecting?', but I don't know a command that will let me do that. If anyone can tell me such a command, I'd appreciate it.
The error means that:
If-None-Match: xyz
(previous etag, there can also be multiple such etags if you have done many builds and got different results from the URL).Because some servers misbehave we allow a case where 304 doesn't contain etag and request only contained one to consider that the one we sent was matching. But in this case server does seem to send etag but it is not the correct one that should cause 304.
You can't see the raw etag metadata via API. What you can do is find the previous cache record from buildx du --verbose
via the description and then prune it with --filter id=value
filter.
My build, which was working fine previously, is failing because of an error with a cache key:
The relevent part of the compose file:
And the Dockerfile:
The version of Docker I'm using:
The image from the previous, successful build:
The version of https://ssl-config.mozilla.org/ffdhe2048.txt currently being served is identical to that stored in the latest successful build, and the ETag currently being returned is in fact "65a0156d-1a7":
(I'd like to check what the ETag stored in the build cache is, but I can't find any command that will show me this information.)
Related issues: #905 and #2832 both describe the same issue. Both are marked as closed.
Further testing: I can delete the existing image and rebuild from scratch, without the cached build. I've held off in case there is other information to be gleaned from the old image before I delete it (such as what ETag it expects for that ADD command).