I attempted to host the image from docker hub to azure and for the first time the credentials supplied went well . But after a re-start of the container , it is having credentials issue . And I'm not sure where the credentials can be supplied . Any help >
Asked
Active
Viewed 94 times
0
-
could you please provide mow info /context. I don't understand where the error comes from ? Maybe share the CLI command you used or the ARM template ? – djsly Jul 04 '20 at 22:37
-
Hi @djsly , I did not use CLI to create the container . Rather used the Azure portal to create a container and chose the option of using a public docker image which I pulled using my Docker credentials . Does this helps – Rajesh Rajamani Jul 05 '20 at 06:38
-
How do you encounter the error ? How to you restart it ? – djsly Jul 05 '20 at 14:30
-
The error appears each time when you restart the container in the Azure portal? – Nancy Jul 08 '20 at 07:24
-
Hi @NancyXiong yes . It is not the case if the image is a public image which obviously removes the need for a credential . As Im testing I did not want to use the space in the Azure Container Registry for time-being as it costs some dollars . – Rajesh Rajamani Jul 08 '20 at 10:23
-
Ensure that the image exists in the registry, and that you've typed the image name correctly. Try to remove this ACI then re-deploy it via Azure portal again? Is this error still existed? Or check the [diagnostic logs](https://learn.microsoft.com/en-us/azure/container-instances/container-instances-get-logs#get-diagnostic-events). – Nancy Jul 08 '20 at 10:43
-
can you try issuing the restart not using the portal ? az cli maybe ? maybe the restart payload removed some credentials from the internal resource. – djsly Jul 08 '20 at 20:33
-
also, can you get the output of your container object using resources.azure.com before and after the restart to see if the container fields are different. – djsly Jul 08 '20 at 20:33
-
Can you share the screenshot that you create the container instance in the portal? – Charles Xu Jul 21 '20 at 07:00
-
Do you still work on this issue or you already solve it? – Charles Xu Jul 23 '20 at 01:47
-
It got resolved without having to do anything special . At the moment I'm able to restart the container without any issues – Rajesh Rajamani Jul 28 '20 at 11:49