This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(249.60000000000002, 34%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGO%3C/text%3E%3C/svg%3E)
I received notification this morning at 08:02 that there was an availability error in my application. The App Service could not reach the container via the ip address I had configured, 10.24.2.5. I login to the portal to check and it seems the ip address of my container instances has changed to 10.24.2.4. According to the documentation
If the container group is stopped, started, or restarted, the container group's private IP is subject to change. If this happens, you will need to update the application gateway configuration.
I do not know why my container group was stopped, started or restarted, however I noticed a couple of events in the log which coincide with the time the incident occurred.
This is strange to me, as there was nothing I did overnight to prompt azure container instances to try and fetch a new image. The image it's pulling is hosted in an Azure Container Registry, and from the portal we can see that this image has not changed since June 2020 and so pulling should not cause any stop/start/restart to occur.
Can someone please explain why in the middle of the night, azure container instances takes it upon itself to try and pull a new version of my image, restarts itself and then gets a new ip address?
Can you check the activity log for the container instance and see if there is anything in there?
Nothing in the activity log over the last 24 hour period
I've also checked the log file for the container itself and there is no errors or crashes reported there that would cause it to restart either. There is nothing between the time it was last started, and the time where it started up again.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(121.6, 71%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDB%3C/text%3E%3C/svg%3E)
We've had the same issue but our restart policy was set to always, we are changing it to onfailure and also specifying the IP for the container instance to avoid changing IPs.
https://learn.microsoft.com/en-us/azure/container-instances/container-instances-troubleshooting
Can you specify the ip address when it's a private ip?
ironically we've had the same issue even after specifying private IP addresses. to get around this we are using a smaller subnet range for these container instances to better manage the IPs they will receive.
Maybe it's because I'm deploying my infrastructure with terraform, but I don't have an option to set a private ip address for the container instances explicitly, only a subnet. Can you let me know how you were able to assign a static private ip to this resource?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(89.60000000000001, 28.999999999999996%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERE%3C/text%3E%3C/svg%3E)
I'm facing the same issues. We have several containers, all deployed with RestartPolicy="OnFailure", but they keep randomly pulling the image and therefore containers are restarted and most of the time changing their IP addresses. We have others processes that depend on that private IP address so if it changes, this breaks things.
The image hasn't changed so I don't understand what else could be forcing to pull the image again.
@Gareth Oates @Rodrigo Espinoza Have either of you created a CSS case to dive down onto why the image was pulled?
I have yes, but so far it has just been gathering information from logs, screenshots etc. no reply yet about what is causing this to occur. It's comforting to know I'm not the only one in this position though.
Can you share the Support Request # (SR#) with me? I would love to follow the issue.
Your best bet for this situation is to follow up with support. They have better access to logs & troubleshooting to try and figure out why this is happening.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(12.8, 6%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESC%3C/text%3E%3C/svg%3E)
Anybody get to the bottom of why this happened ?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(92.8, 98%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EC%3C/text%3E%3C/svg%3E)
The same happened to our ACI setup as well, just two days ago, for unknown reasons. One container group got restarted but this activity is not shown in the activity log. We store the logs outside in a log analytics workspace so I could see the applications restart sequence as well as the uptime command showed that the container got restarted a few hours ago. I wonder what triggers this restart, so far I have not received a satisfying answer from Microsoft
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Same over here (unknown cause of container restart yesterday). The event log doesn't square with the container state summary in the attached screenshot (that also shows the earlier random image pulling last month). None of the container alerts were tripped either (includes start/stop/restart/start events).
