On-premises kubernetes cluster about mindaro HOT 10 CLOSED

@riker09 Running into the same issue, this wasn't the case a few days ago. Created a separate issue #45 since this doesn't seem to be related to on-prem clusters.

from mindaro.

@riker09, @jamyc - The "Failed to pull image" issue has been resolved. Please let us know if you encounter any other problems.

@muhammed-sumer - Thank you for providing your logs. The team is actively looking into the issue and will provide an update as soon as we have more information.

Thank you,
Nick

from mindaro.

Hi @muhammed-sumer , thanks for reaching out to us!
Can you please provide the logs from "%temp%\Bridge To Kubernetes" folder?

from mindaro.

Hi @pragyamehta, I added the log files. Thanks.

bridge-mindarocli-2020-10-07-06-18-54-13848.txt
bridge-mindarocli-2020-10-07-06-18-58-1644.txt
bridge-library-2020-10-07-06-18-55-13848.txt
bridge-library-2020-10-07-06-18-58-1644.txt

from mindaro.

I've tried to debug the BikeSharingApp running inside a Docker for Desktop cluster. I can see that the redirectional pods are started, however, it fails with this error:

Failed to pull image "bridgetokubernetes.azurecr.io/lpkremoteagent:0.1.4": rpc error: code = Unknown desc = Error response from daemon: Get https://bridgetokubernetes.azurecr.io/v2/lpkremoteagent/manifests/0.1.4: unauthorized: authentication required, visit https://aka.ms/acr/authorization for more information.

The image lpkremoteagent:0.1.4 seems to be hosted on a private Azure Container Registry, is that correct? Shouldn't that be public?

from mindaro.

Thank you for your quick response on this. I will check it out tomorrow. May I ask what has been changed?

from mindaro.

@riker09 Our images reside in an azure container registry, and we had to update the ACR such that our customers could pull images from it successfully.

from mindaro.

@muhammed-sumer We have released the fix for your issue. Please try again and let us know if you are unblocked now!

from mindaro.

Hi @pragyamehta, That's great. It worked in local environment after the update. I will also try it on the internal kubernetes server. I will share my experiences with you again. Thank you..

from mindaro.

Closing the issue. Thanks for reporting it!

from mindaro.