You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a private function published in my private registry. Even if I use docker login, the crossplane beta render still fails with:
crossplane: error: cannot render composite resource: cannot start Function "function-aws-data": cannot pull Docker image "harbor.local/enterprise.ghcr.io/my-org/crossplane-function-aws-data:v0.0.17": Error response from daemon: unauthorized: unauthorized to access repository: enterprise.ghcr.io/my-org/crossplane-function-aws-data, action: pull: unauthorized to access repository: enterprise.ghcr.io/my-org/crossplane-function-aws-data, action: pull
I verified that I can in fact docker pull my function image just fine, and after I pull it manually the crossplane beta render starts to work just fine too.
My private registry is Harbor in case that matters, and my local environment I run the crossplane beta render command is a MacOS M1 running Rancher Desktop in K3d mode.
How can we reproduce it?
Try to crossplane beta render on a composition using a private image, I guess.
What environment did it happen in?
Crossplane version: v1.15.0
The text was updated successfully, but these errors were encountered:
What happened?
I have a private function published in my private registry. Even if I use
docker login
, thecrossplane beta render
still fails with:I verified that I can in fact
docker pull
my function image just fine, and after I pull it manually thecrossplane beta render
starts to work just fine too.My private registry is Harbor in case that matters, and my local environment I run the
crossplane beta render
command is a MacOS M1 running Rancher Desktop in K3d mode.How can we reproduce it?
Try to
crossplane beta render
on a composition using a private image, I guess.What environment did it happen in?
Crossplane version: v1.15.0
The text was updated successfully, but these errors were encountered: