bridgetokubernetes.azurecr.io/routingmanager:stable not found 404
letmagnau opened this issue · 8 comments
Describe the bug
docker not found bridgetokubernetes.azurecr.io/routingmanager:stable, not exist anymore
Mention the platform you are using
vscode
To Reproduce
Steps to reproduce the behavior:
classic use of b2k on vscode
Expected behavior
routing manager have to be running... but not
Screenshots
Logs:
- Please attach logs for Bridge to Kubernetes to triage issues faster, here are the log locations ( Window like C:\Users\Username\AppData\Local\Temp\Bridge To Kubernetes, Linux/Mac like $HOME/tmp/Bridge To Kubernetes or /tmp/Bridge To Kubernetes). Please attach logs relevant to your issue or bug.
Desktop (please complete the following information):
- OS: Manjaro
Looks like the issue is caused by this PR: #602
_"Old ACR will be deleted and will be announced to users that they need to update to latest version before releasing this to marketplace."
thanks for reply , but How can I switch to new repo, using vscode or bash tool?
It seems not released in new product versions
You can point it at other ACRs using these 3 environment variables
BRIDGE_DEVHOSTIMAGENAME
BRIDGE_RESTORATIONJOBIMAGENAME
BRIDGE_ROUTINGMANAGERIMAGENAME
However it appears we can't point it at the new repo yet anyway.
Error response from daemon: Head "https://bridgetok8s.azurecr.io/v2/lpkremoteagent/manifests/1.3.4": unauthorized: {"errors":[{"code":"UNAUTHORIZED","message":"authentication required, visit https://aka.ms/acr/authorization for more information."}]}
seems not work on vscode, how can I set this env?
The images are deployed back to old ACR repositories (bridgetokubernetes.azurecr.io), can you all please retest and confirm here?
Yes it is working now.
Closing this issue as it works. Please feel free to open it again if anyone faces this issue again. Thank you all.