Docker.io proxy cache isn't tagging official images

[ijustworkhereshrug]

Expected behavior and actual behavior:
When pulling an image from docker.io, all images should be tagged. However, we're seeing that any "official" images from docker.io, that contain "library" in the image path are not getting tagged

Steps to reproduce the problem:

1. Create a Proxy Cache repository pointed at docker.io
2. Pull an "official" docker.io image, which contains "library" in the path or implied by not having an organization tag. (eg. ${harbor_url}/docker.io/library/httpd:2.4.41)
3. Check the docker.io proxy, locate the pulled image and check that the tag does / does not exist

Versions:

• harbor version: v2.12.2-73072d0d (also failed on previous versions of Harbor)
• High-availability / multi-az deployed Helm Chart, using AWS RDS, S3, and Elasticache.

Additional context:

• When pulling an image from docker.io, if library isn't specified (eg. ${harbor_url}/docker.io/httpd:2.4.41) it is still implied and will show up with "library" in the path for the image.

• When pulling organizational image (non-official docker.io images), such as ${harbor_url}/docker.io/cypress/included:13.13.0, the image will get tagged

[bupd]

Yes this exists.

ON UI

ON API

[ijustworkhereshrug]

I tested out a few images on the official Harbor Demo site. It seems a bit random if it works or doesn't work:
Harbor Docker.io Project

[ijustworkhereshrug]

It seems like it's more reliably not tagging images, if they're deleted and repulled

[stonezdj]

The creation of tag is not garanteed, especially for image indexes( with folder icon in the UI)

[ijustworkhereshrug]

Interesting. Can you explain why? From my perspective that's a big bug.

For my use-case, this is rather important for replication and airgapping images, since it's not visible when pulling from the UI or API. We need to be able to pull tags reliably from Proxy Repos