Open JoeMarkov opened 1 year ago
Also, deploying the same image from Azure Portal results in the same error
route to CXP team
Seeing the same issue via terraform
@JoeMarkov Thanks for noting that 1.41 still works.
'also, trying to create Jaeger via Docker fails on version 1.41 fails for me, but this time, it never completes...
docker --context myacicontext run -d --name observabilty-jaeger --domainname observabilty-jaeger --cpus=".5" --memory="0.5" -e COLLECTOR_ZIPKIN_HOST_PORT=:9411 -p 5775:5775/udp -p 6831:6831/udp -p 6832:6832/udp -p 5778:5778 -p 16686:16686 -p 14268:14268 -p 14250:14250 -p 9411:9411 jaegertracing/all-in-one:1.41
It should not take many minutes for this to deploy, but it hangs....
Related command
az container create -g Observabilty --name test13313323 --image jaegertracing/all-in-one:latest
Describe the bug
I can't create the public image above, I get this error: (InaccessibleImage) The image 'jaegertracing/all-in-one:latest' in container group 'test' is not accessible. Please check the image and registry credential. Code: InaccessibleImage
But running it locally works fine using docker pull jaegertracing/all-in-one:latest
However, tag 1.41 works:
az container create -g $rgname --name $JaegerContainerName --image jaegertracing/all-in-one:1.41
So, why does not 1.42 or latest work?
To Reproduce
Expected behavior
I would expect that all public containers on Github was deployable:
az container create -g MyResourceGroup --name test123--image jaegertracing/all-in-one:latest
Environment summary
Additional context