We see this in /artifactory/api/storageinfo
usedSpace: "412.72 GB",
However, we have only uploaded ~1900 files, totalling ~156Gb. The difference
is in the way client and server are handling reused docker image layers.
We are following good practice and automatically building new images as part
of our CI pipeline where the top layer is generally the only changing layer.
When pushing, most of the layers are not pushed as artifactory returns
'Layer already exists'.
The artifactory doc also implies shallow copy/links are used to handle
knowing when orphaned layers can be deleted.
Example - two consecutive, automated image publishes:
4 layers are common, ~2.7Gb. 1 layer changes, 10Kb each time.
Docker push/artifactory knows this, as it reports `Layer already exists¿.
The storage info should be ~2.7Gb, not ~5.4Gb and the storageinfo REST call
should reflect the activiyy from the client's perspective including docker