Vincent Ambo 48a5ecda97 feat(server): Order layers in image manifest based on merge rating ... Image layers in manifests are now sorted in a stable (descending) order based on their merge rating, meaning that layers more likely to be shared between images come first. The reason for this change is Docker's handling of image layers on overlayfs2: Images are condensed into a single representation on disk after downloading. Due to this Docker will constantly redownload all layers that are applied in a different order in different images (layer order matters in imperatively created images), based on something it calls the 'ChainID'. Sorting the layers this way raises the likelihood of a long chain of matching layers at the beginning of an image. This relates to #39.		2019-10-03 22:50:02 +01:00
..
archive.go	feat(server): Implement creation of layer tarballs in the server	2019-10-03 22:29:50 +01:00
builder.go	feat(server): Order layers in image manifest based on merge rating	2019-10-03 22:50:02 +01:00
cache.go	feat(server): Reimplement local manifest cache backed by files	2019-10-03 13:21:04 +01:00