InternalServerError while creating ACI group with two containers

Question

I'm trying to create an ACI group with two containers named seq and reverse-proxy using the file iastse720-seq-aci-deployment-v4.txt. Because DockerHub recently limited anonymous access to public images, I'm also passing the username and personal access token to be considered an authenticated user.

I first executed the command below from Cmder to log in to Tenant.

az login --tenant tenantIdHere

Then I tried the below command for creating a container group

az container create --resource-group IATSE720 --file iastse720-seq-aci-deployment-v4.yaml --debug

I got an error message, as shown below. I also attached the entire Cmder response in another text file, Cmder response for v4 execution.txt.

Please assist me in identifying the root cause of the Internal Server Error response from Azure Management.

Answer 1

I work for a client who also has the Developer Plan. To receive priority support, I have added myself to the Contributor Support Role. However, even though I am using the same email address, I am not entirely sure if Microsoft can see this for this user.

I was desperate to resolve the issue, so I didn't examine your last comment. I was aware of using ACR but was not keen on it to avoid unnecessary complexity. Consequently, I exported a YAML script for my existing similar setup without persistent storage.

Then, I created a new YAML using a hit-and-try approach. Eventually, I found the YAML that worked.

additional_properties: {}
apiVersion: 2023-02-01-preview
extended_location: null
location: centralus
name: iatse_seq
properties:
  containers:
    - name: seq
      properties:
        configMap:
          keyValuePairs: {}
        environmentVariables:
          - name: ACCEPT_EULA
            value: Y
          - name: SEQ_API_LISTENURIS
            value: http://localhost:8080
        image: datalust/seq:latest
        ports:
          - port: 8080
            protocol: TCP
        resources:
          requests:
            cpu: 1.0
            memoryInGB: 2.0
        volumeMounts:
          - name: seq-storage
            mountPath: /data        
    - name: caddy
      properties:        
        configMap:
          keyValuePairs: {}
        environmentVariables: []
        image: caddy:latest
        ports:
          - port: 80
            protocol: TCP
          - port: 443
            protocol: TCP
        resources:
          requests:
            cpu: 0.5
            memoryInGB: 0.5
        volumeMounts:
          - name: proxy-caddyfile
            mountPath: /etc/caddy
          - name: proxy-data
            mountPath: /data
          - name: proxy-config
            mountPath: /config        
  initContainers: []
  ipAddress:
    autoGeneratedDomainNameLabelScope: Unsecure
    dnsNameLabel: iatse-logs
    fqdn: iatse-logs.centralus.azurecontainer.io
    ports:
      - port: 80
        protocol: TCP
      - port: 443
        protocol: TCP
    type: Public
  imageRegistryCredentials:
    - server: index.docker.io
      username: vssaini
      password: personal-access-token  
  isCreatedFromStandbyPool: false
  isCustomProvisioningTimeout: false
  osType: Linux
  volumes:
    - name: proxy-caddyfile
      azureFile:
        shareName: fs-proxy-caddyfile
        storageAccountName: iatseseqacist
        storageAccountKey: storage-account-key
    - name: proxy-data
      azureFile:
        shareName: fs-proxy-data
        storageAccountName: iatseseqacist
        storageAccountKey: storage-account-key
    - name: proxy-config
      azureFile:
        shareName: fs-proxy-config
        storageAccountName: iatseseqacist
        storageAccountKey: storage-account-key
    - name: seq-storage
      azureFile:
        shareName: fs-seq
        storageAccountName: iatseseqacist
        storageAccountKey: storage-account-key
  provisioningTimeoutInSeconds: 1800
  sku: Standard
tags: null
type: Microsoft.ContainerInstance/containerGroups

I have attached the respective file, seq-aci-deployment.txt, for others to reference. Change the extension to YAML. :)

The possible reason for the issue: I am not sure, but I believe I might have used the volumes in the wrong position in the YAML file, which could have caused the internal server error. 

I wish someone from Microsoft would have given me the exact reason for the error.

Note for Volumes: Please create file shares as illustrated below. There is no requirement to create any directories within the file shares. Lastly, upload the Caddyfile without an extension. 

The content of my Caddyfile is

iatse-logs.centralus.azurecontainer.io {
    reverse_proxy http://localhost:8080
}