Azure Container Instances
An Azure service that provides customers with a serverless container experience.
ACI container is still running after deletion of container instance
![](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(150.4, 70%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDL%3C/text%3E%3C/svg%3E)
Dennis Lerche
0
Reputation points
I have a container instance that I have deleted, after deletion I re-deployed the container instance with the same name, however I can see that the old container is still running as I can ping that IP and the new container instance gives an ip higher than previously.
How can I get the invisible container deleted as I cannot see it, but can see that it exists as the ip answers.
According to this https://learn.microsoft.com/uk-ua/troubleshoot/azure/azure-container-instances/management/aci-still-running-after-stop-delete-command the re-deploy should have solved it, but I have tried several times with no luck.
Azure Container Instances
{count} votes
-
![](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(0, 80%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESP%3C/text%3E%3C/svg%3E)
Shraddha Pandey 565 Reputation points Microsoft External Staff Moderator2025-12-19T13:58:41.53+00:00 Hi Dennis Lerche,
it sounds like you're encountering a frustrating situation with your Azure Container Instance (ACI). Here's what you can try to resolve the issue where an old container instance appears to be still running even after you've deleted it:
- Verify Deletion: First, double-check that the deletion command has been executed properly. You can do this using the Azure CLI with the command:
Replaceaz container list --resource-group <yourResourceGroup> --output table<yourResourceGroup>with the name of the resource group your container is in. The deleted container should not show up in the output. - Re-deploy with Same Resource ID: As the document you referenced suggests, if the container still appears to be running, create a new container instance with the same resource ID in the same region. You can do this with the Azure CLI or through the Azure portal. Upon successful creation, it should trigger the deletion of the old instance.
- Check Billing: Verify if the old container instance is still incurring charges to confirm that it is indeed still active.
If these steps don't resolve the issue, you may need to take more specific action based on your observed behaviors.
Follow-Up Questions:
- Can you confirm if you executed the deletion command successfully and if it returned a success message?
- What method are you using to check the running instances (CLI, portal, etc.)?
- Have you tried creating a new instance with the same resource ID, and did it provide any error messages?
- Are you noticing any billing related to the container that you expect to be deleted?
Hope this helps, and let me know if you need further assistance!
References:
- Verify Deletion: First, double-check that the deletion command has been executed properly. You can do this using the Azure CLI with the command:
-
Dennis Lerche 0 Reputation points
2025-12-19T14:00:14.9333333+00:00 I'm sorry but that looks like an auto-generated answer as all those things have been done, hence the link I provided.
Sign in to comment
Sign in to answer