Container stuck in "Waiting" state

Fahad Mustafa 16 Reputation points
2021-06-09T23:41:07.12+00:00

Hi,

I have an ACI that was running fine but suddenly stopped and cannot restart. The container state is stuck in the "Waiting" state. Attempts to redeploy fail after 30 mins timeout.

I'm deploying through GitHub actions. I see this log:

Created container;Started container;Subscription deployment didn't reach a successful provisioning state after '00:30:00'.;Subscription deployment didn't reach a successful provisioning state after '00:30:00'.;Subscription deployment didn't reach a successful provisioning state after '00:30:00'.".

Image is hosted on GitHub's docker repo.

I've pulled and run the container locally without issues.

I've also deleted the container instance and created again. No luck there.

Azure Container Instances
Azure Container Instances
An Azure service that provides customers with a serverless container experience.
700 questions
{count} votes

7 answers

Sort by: Most helpful
  1. Rodrigo Espinoza 11 Reputation points
    2021-06-15T04:48:19.41+00:00

    This problem persists as long as I redeploy the container with the same name...if I create a new ACI with different name and pull from the same image, it works fine. I guess Azure is failing to deallocate resources when a container is deleted..so if it's deploy under the same name somehow get's the previous state/resources

    2 people found this answer helpful.
    0 comments No comments

  2. Kaderli Manuel 6 Reputation points
    2021-10-21T05:58:02.023+00:00

    Same problem. When i deploy the container with the same name, it remains stuck (waiting).
    When i deploy it with a new name, it starts

    1 person found this answer helpful.

  3. Tillin, Dan (OAG) 6 Reputation points
    2021-11-04T09:03:51.543+00:00

    Did anyone get a resolution? i have the same problem.
    Tried using a different region, but container still in a waiting state

    1 person found this answer helpful.
    0 comments No comments

  4. Rodrigo Espinoza 11 Reputation points
    2021-06-15T04:43:27.563+00:00

    I have exactly the same problem. 4 of our containers have crushed and they haven't been able to recover since then. I decided to delete them and redeployed them again. They all got stuck with state "waiting" (and the container group's status remains as "Creating")

    105646-image.png

    105587-image.png


  5. Josh Parker 11 Reputation points
    2021-12-20T17:22:46.957+00:00

    For anyone using terraform (or similar) to manage infrastrucure, one workaround is to append random id to the container name. e.g.,

    resource "random_id" "id" {
      byte_length = 8
    }
    
    resource "azurerm_container_group" "containers" {
      ...
      container {
        name    = "${local.container_name}-${random_id.id.hex}"
      }
    }
    

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.