Assuming that a.b.c/ns/img:1.0 , a.b.c/ns/img:latest are same single-architecture images with diff tags
and convertor -db xxx -r a.b.c/ns/img -i 1.0 -o 1.0_accelerated has been successfully executed.
At this point, the conversion cache is also recorded in the database.
then we run convertor -db xxx -r a.b.c/ns/img -i latest -o latest_accelerated
it will succeed directly with db cache.
However, the new tag a.b.c/ns/img:latest_accelerated will not be uploaded.
What did you expect to happen?
a new image tag should also be uploaded if a cache was found in the database during the dup convert process.
a.b.c/ns/img:latest_accelerated should also be uploaded
How can we reproduce it?
As mentioned in the section What happened in your environment?
What is the version of your Accelerated Container Image?
What happened in your environment?
Assuming that
a.b.c/ns/img:1.0,a.b.c/ns/img:latestare same single-architecture images with diff tagsand
convertor -db xxx -r a.b.c/ns/img -i 1.0 -o 1.0_acceleratedhas been successfully executed. At this point, the conversion cache is also recorded in the database.then we run
convertor -db xxx -r a.b.c/ns/img -i latest -o latest_acceleratedit will succeed directly with db cache. However, the new tag
a.b.c/ns/img:latest_acceleratedwill not be uploaded.What did you expect to happen?
a new image tag should also be uploaded if a cache was found in the database during the dup convert process.
a.b.c/ns/img:latest_acceleratedshould also be uploadedHow can we reproduce it?
As mentioned in the section
What happened in your environment?What is the version of your Accelerated Container Image?
v1.2.3
What is your OS environment?
Ubuntu 22.04
Are you willing to submit PRs to fix it?