Thank you! I actually found a successful workaround by setting up the container instance to pull from dockerhub instead of the Azure container registry. I can still provide the details via email if you're interested.
Successful Azure Container Instance, Able to start/restart. 6 hours later: Failed to start the container group 'clever-kowalevski'. Error: The image in container group is not accessible. Please check the image and registry credential.
Christopher Ranck
1
Reputation point
Built the Container Instance from the Container Registry, originally from Docker (Ubuntu 20.04).
It seems that a few hours later, I cannot start, stop or restart the container instance. Looking at the JSON logs of the successful run and unsuccessful runs, the successful run has one extra line:
'Claims":{ "wids": which is not in the log from the unsuccessful run.
Full error portion of JSON from unsuccessful run:
I'm been searching around here and stackoverflow but not finding a lot of information on what might be wrong.
Azure Container Registry
Azure Container Registry
An Azure service that provides a registry of Docker and Open Container Initiative images.
508 questions
Azure Container Instances
Azure Container Instances
An Azure service that provides customers with a serverless container experience.
757 questions