DevSpace - The Fastest Developer Tool for Kubernetes ⚡ Automate your deployment workflow with DevSpace and develop software directly inside Kubernetes.
What did you expect to happen instead?
Logging in with az acr login with your private account should work in the same way as logging in with an admin account. It should atleast give a clear error message about why the secret was not created.
How can we reproduce the bug? (as minimally and precisely as possible)
Use acr as container registry and login to this with az acr login
Setup pull-secret in devspac.yaml targeting acr
Run devspace deploy and see that no "devspace-pull-secrets" is created and no error messages are printed.
What happened?
When using recommended login to Azure Container Registry:
the entry in .docker/config.json is not accepted by devspace when using the Pull Secrets capability.
Running
does not create a pull-secret. After printing "Ensuring image pull secret for registry:", the create part never happens.
If we instead use the Azure Container Registry admin account for login:
This works as expected when deploying with devspace:
The difference between the .docker/config.json az acr login:
docker login with admin account
What did you expect to happen instead?
Logging in with
az acr login
with your private account should work in the same way as logging in with an admin account. It should atleast give a clear error message about why the secret was not created.How can we reproduce the bug? (as minimally and precisely as possible)
az acr login
devspace deploy
and see that no "devspace-pull-secrets" is created and no error messages are printed.My devspace.yaml:
Local Environment:
Anything else we need to know?
/kind bug