Thank you for this blog. This indeed seems to be the right way to build and publish images. When I recently started using docker-image for this purpose, it didn’t seem right that the docker image was getting built in a [put] step, until I came across this blog. It would be nice to add a reference to this blog in the README file for docker-image resource.
I do have few comments/questions about the registry-image and the oci-build-task approach. The docker-image seems to support many features that could be missing here or seem to be not documented. For example, does it support the following attributes:
For what I want, I am building an image with oci-build-task, pushing it to private docker registry using registry-image and then have a 2nd oci-build-task which loads the image built in the first step and build another docker image and push it to our private docker registry. However, I am not sure how to implement the 2nd part as it is not able to load the docker image built in the first step.