Unable to create azure container group with chromadb/chroma image

Docker Hub
, ,
1

I get following error when trying to create my azure container group with the docker image chromadb/chroma using terraform:

Error: creating Container Group (Subscription: ""
│ Resource Group Name: ""
│ Container Group Name: "chroma-db"): performing ContainerGroupsCreateOrUpdate: unexpected status 409 (409 Conflict) with error: RegistryErrorResponse: An error response is received from the docker registry 'index.docker.io'. Please retry later.

I checked my pull rate limit and that can’t be the issue (I authenticated using docker login):

ratelimit-limit: 200;w=21600
ratelimit-remaining: 199;w=21600

It used to work just fine. Any ideas what the issue might be?

This is my terraform resource:

resource "azurerm_container_group" "chroma-db" {
  name                = "chromadb"
  location            = var.location
  resource_group_name = data.terraform_remote_state.foundation.outputs.resource_group_name
  os_type             = "Linux"
  ip_address_type     = "Private"
  subnet_ids          = [data.terraform_remote_state.foundation.outputs.chroma_subnet_id]

  container {
    name   = "chroma-db"
    image  = "chromadb/chroma:latest"
    cpu    = "1"
    memory = "2"

    environment_variables = {
      CHROMA_SERVER_AUTHN_CREDENTIALS = var.chroma_server_authn_credentials
      CHROMA_SERVER_AUTHN_PROVIDER    = var.chroma_server_authn_provider
    }

    ports {
      port     = 8000
      protocol = "TCP"
    }

    volume {
      name                 = "chroma-db-volume"
      mount_path           = "/chroma/chroma"
      storage_account_name = data.terraform_remote_state.foundation.outputs.storage_account_name
      storage_account_key  = data.terraform_remote_state.foundation.outputs.storage_account_primary_access_key
      share_name           = data.terraform_remote_state.foundation.outputs.storage_share_name
    }
  }
}
2

Can you run the same commands manually using the docker cli? Based on the HTTP status code my guess is that the client sends incorrect requests to the registry. I have no idea what request it is as it is not mentioned in the error message.