container stuck in waiting state

rayden 41 Reputation points
2022-10-11T09:49:16.92+00:00

Hi,

It's my first time deploying containers in azure, I used docker compose for the deployment of odoo + postgres, the deployement went fine for the odoo container but in the other hand postgres is stuck in "waiting" state.

Here's my docker compose :

version: '3.2'  
    services:  
      odoo:  
        image: odoocontainerregistry.azurecr.io/containergroup:postgres  
        env_file: .env  
        depends_on:  
          - postgres1  
        ports:  
          - "127.0.0.1:8069:8069"  
        volumes:  
          - data:/var/lib/odoo  
          - extra-addons:/mnt/extra-addons  
            
      postgres1:  
        image: odoocontainerregistry.azurecr.io/containergroup:postgres  
        env_file: .env  
        volumes:  
          - db:/var/lib/postgresql/data/pgdata  
      
    volumes:  
      data:     
        driver: azure_file  
        driver_opts:  
          share_name: odoofileshare  
          storage_account_name: odooaccount1  
      db:  
        driver: azure_file  
        driver_opts:  
          share_name: odoofileshare  
          storage_account_name: odooaccount1  
      
      extra-addons:  
        driver: azure_file  
        driver_opts:  
          share_name: odoofileshare  
          storage_account_name: odooaccount1  
  

249344-capture.jpg

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

1 answer

Sort by: Most helpful
  1. SUNOJ KUMAR YELURU 13,956 Reputation points MVP
    2022-10-11T15:50:01.667+00:00

    Hi @rayandenfir-1568

    Thanks for using Q & A forum.

    check on deployment logs to Enable debug logging:

    If your container fails to deploy successfully, review the diagnostic information provided by the Azure Container Instances resource provider.

    Azure CLI

     az container logs --resource-group myResourceGroup --name mycontainer  
    

    Previously I too have same issue, after changing different container name it works fine.

    ---
    If this answers your query, do click Accept Answer and Up-Vote for the same. And, if you have any further query do let us know.

    1 person found this answer helpful.