top | item 40943696 (no title) jtmarmon | 1 year ago I’m no expert on docker but I thought the hashes for each layer would already be computed if your image is built discuss order hn newest cpuguy83|1 year ago It's complicated. If you are using the containerd backed image store (opt-in still) OR if you push with "build --push" then yes.The default storage backend does not keep compressed layers, so those need to be recreated and digested on push.With the new store all that stuff is kept and reused. wofo|1 year ago That's true, but I'd assume the server would like to double-check that the hashes are valid (for robustness / consistency)... That's something my little experiment doesn't do, obviously.
cpuguy83|1 year ago It's complicated. If you are using the containerd backed image store (opt-in still) OR if you push with "build --push" then yes.The default storage backend does not keep compressed layers, so those need to be recreated and digested on push.With the new store all that stuff is kept and reused.
wofo|1 year ago That's true, but I'd assume the server would like to double-check that the hashes are valid (for robustness / consistency)... That's something my little experiment doesn't do, obviously.
cpuguy83|1 year ago
The default storage backend does not keep compressed layers, so those need to be recreated and digested on push.
With the new store all that stuff is kept and reused.
wofo|1 year ago