After authenticating to private docker registry (and actually able to pull the image!), running a docker action that uses private image hosted in said registry does not seem to work.
A workaround to this is to simply pull the private image manually prior running the action using the image; but this is non ideal if multiple private images are used.
Is this a bug? Will there be any future updates to have docker action pull private images automatically?
- I initially found the issue while trying to run docker actions with private images hosted on AWS ECR, so I do not think this is dockerhub or
- The private image in example repo is simply the current
s4nji/alpine:latestas a private image on dockerhub.
- There is this related topic but looks like it ended up adding private registry support for only job and service containers