Azure devops docker service connection's service principal been removed

 

An issue with an Azure DevOps Docker service connection where the service principal is no longer available. As I have limited access to my organization AD, I am unable to carry out much investigation. I suspect the service principal has been removed.

This is not the same as service principal expired where you can

For expired service principal token

  • Go to your Azure DevOps project settings and navigate to Service connections.
  • Locate the Docker service connection using a service principal.
  • Click Edit on the connection.
  • In the edit window, click Verify. This attempts to refresh the token using the existing credentials.

In my case, didn't even have a "verify" button - so i suspect this is more for Azure ARM Manager. 

Or a variation of the workaround from stackoverflow link where you need to remove the secret before making meaningless update to re-generate the secret.

To resolve it, i have to change my Docker service connection to use "Other" and setup the following 




Why didn't I consider using Managed Identity for this setup? The managed identity is suitable for use-case scenario whereby you have a VM running as an agent pool that pushes images to your ACR.

I didn't wanted to re-create the docker service connection because there's 30 over projects tied to this. 













Comments

Post a Comment

Popular posts from this blog

gemini cli getting file not defined error

Image
 While trying to run gemini cli on my windows linux subsystem, i bump into this error here - "/Roaming/npm/node_modules/@google/gemini-cli/node_modules/undici/lib/web/webidl/index.js:512 webidl.is.File = webidl.util.MakeTypeAssertion(File)"  "ReferenceError: File is not defined" In Node.js, there’s no built-in File (until very recent Node 20+ with experimental WHATWG APIs). So, unless polyfilled, File is undefined, leading to the ReferenceError. And to resolve this, I had to upgrade to node 22 (might work for node 20) and then I was able to run it.
Read more

NodeJS: Error: spawn EINVAL in window for node version 20.20 and 18.20

Encounter this issue when running autorest (that uses nodejs).  I am using node version:  v18.20.2 After i revert to use node v18.12.0, then i was able to get my app to run without this error. Since i am working with Azure devops yaml, i was able to use the following to resolve my issue.  - task : NodeTool@0   inputs :     versionSource : 'spec'     versionSpec : '18.18.0'
Read more

vllm : Failed to infer device type

Trying to run vllm without gpu will typicaly lands you into this issue. To resolve this issue: we can use set these both. Setting one does not work for me. So i had to configure both settings below:- 1.  environment variable CUDA_VISIBLE_DEVICES = "" 2. in the command line, change to use device cpu and remove  tensor-parallel-size. For example, python3 -m vllm.entrypoints.openai.api_server --port 8080 --model deepseek-ai/DeepSeek-R1 --device cpu --trust-remote-code --max-model-len 4096" References https://docs.vllm.ai/en/latest/getting_started/troubleshooting.html#failed-to-infer-device-type
Read more