container_push inside another rule

[ex0ns]

I am currently writing a rules to replace container_run_and_*** on machines that don't have access to docker's socket. In order to achieve that I used remote buildkit agent that take care of building the image and returning a tar image that can be used by the rest of the docker rules commands.

The issue is that buildkit does not have a local image repo as docker does, so we can't simply build image from a tar under a local name and then use them as a base for another image. My idea to bypass this limitation is to build those temporary image using container_image and then push them with a temporary, unique tag on our artifactory, this way I could use the newly generated tag as a base for my rules builctl_run_and_****.

container_image does expose its internal using a struct in image.bzl, however container_push does not, and I would like to understand why ? Why is container_push limited to the loading phase ? Is there a valid reason for that ?

I hope that I was able to explain my problem
ps: if you have a better idea, I would love to hear it, but as of now I'm pretty stuck with this setup.