Provide instructions, a fix, or guidance on fixing authorization errors when diffing images on Azure container registry

[David-Noble-at-work]

In short, I would like this command to work:

container-diff diff <registry-name>.azurecr.io/<image-name-1> <registry-name>.azurecr.io/<image-name-2> --verbosity debug

Expected behavior

Difference between the two images.

Actual behavior

Authorization error:

INFO[0000] starting diff on images  <registry-name>.azurecr.io/<image-name-1>  and  <registry-name>.azurecr.io/<image-name-2>, using differs: [size]
INFO[0000] retrieving image: <registry-name>.azurecr.io/<image-name-1> 
INFO[0000] retrieving image: <registry-name>.azurecr.io/<image-name-2>
ERRO[0001] error retrieving image <registry-name>.azurecr.io/<image-name-1>: retrieving remote image: UNAUTHORIZED: aad access token with sp failed client id must be guid
error retrieving image <registry-name>.azurecr.io/<image-name-2>: retrieving remote image: UNAUTHORIZED: aad access token with sp failed client id must be guid 

Information

• container-diff version:

  v0.17.0 built from git (unknown)
  

• Operating system:

  Darwin 22.5.0 Darwin Kernel Version 22.5.0: Mon Apr 24 20:52:24 PDT 2023; root:xnu-8796.121.2~5/RELEASE_ARM64_T6000 arm64 arm Darwin
  

Steps to reproduce the behavior

az login
az acr login --name <registry-name>
container-diff diff <registry-name>.azurecr.io/<image-name-1> <registry-name>.azurecr.io/<image-name-2> --verbosity debug

Steps to workaround this issue

az login
az acr login --name <registry-name>
docker pull <registry-name>.azurecr.io/<image-name-1>
docker pull <registry-name>.azurecr.io/<image-name-2>
container-diff diff daemon://<registry-name>.azurecr.io/<image-name-1> daemon://<repository-name>.azurecr.io/<image-name-2> --verbosity debug

[ankitbko]

This saved my life. This is a must have thing in Readme.