Replies: 1 comment
-
I've been trying to do something along these line too, also without success. We have to protect the IP of the tools that we use, which is why having a publicly accessible docker image is not feasible. Creating an internal docker container works great, however consuming that container as part of an internal action is where I'm getting stuck. I'm sure that other developers, within enterprise organisations, must have wanted to use actions in just this way. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Select Topic Area
Question
Body
Hi All,
I am trying to create new custom docker actions using the private/internal docker image but I am getting unauthorized. Is it even possible to do this?
I even tried to login to the registry before using the custom action but that didn't work too.
Beta Was this translation helpful? Give feedback.
All reactions