Provisioning from private repository on Docker Hub registry fails

[joshualyon]

Attempted deployment of an image from a private repository on DockerHub fails. The provisioning state for the container group is returned as "Failed" via the CLI and the Azure portal shows the container state as "Waiting". Public images from Docker Hub work fine.

Are there additional logs / troubleshooting details that I should be reviewing?

Manually created the resource group using the CLI:

az group create -l eastus -n testcontainers

Then attempted to create the container in the newly created resource group using the image from the private repository on Docker Hub:

az container create -g testcontainers -n twx --image joshualyon/myimage --ip-address public --registry-login-server registry.hub.docker.com --registry-username joshualyon --registry-password {password}

WORKING (Public repository/image):

az container create -g testcontainers -n apache --image httpd --ip-address public

I also noticed that the working deployments happen very quickly (on the order of seconds as noted in the blog post), whereas the failed deployments are taking ~30 minutes.

[joshualyon]

Details of the az container list call:

[
  {
    "containers": [
      {
        "command": null,
        "environmentVariables": [],
        "image": "joshualyon/myimage",
        "instanceView": null,
        "name": "twx",
        "ports": [
          {
            "port": 80
          }
        ],
        "resources": {
          "limits": null,
          "requests": {
            "cpu": 1.0,
            "memoryInGb": 1.5
          }
        },
        "volumeMounts": null
      }
    ],
    "id": "/subscriptions/{subscriptionID}/resourceGroups/testcontainers/providers/Microsoft.ContainerInstance/containerGroups/twx",
    "imageRegistryCredentials": [
      {
        "password": null,
        "server": "registry.hub.docker.com",
        "username": "joshualyon"
      }
    ],
    "ipAddress": {
      "ip": "52.168.84.229",
      "ports": [
        {
          "port": 80,
          "protocol": "TCP"
        }
      ]
    },
    "location": "eastus",
    "name": "twx",
    "osType": "Linux",
    "provisioningState": "Failed",
    "resourceGroup": "testcontainers",
    "restartPolicy": null,
    "state": null,
    "tags": null,
    "type": "Microsoft.ContainerInstance/containerGroups",
    "volumes": null
  },
  {
    "containers": [
      {
        "command": null,
        "environmentVariables": [],
        "image": "joshualyon/myimage",
        "instanceView": null,
        "name": "myname17810",
        "ports": [
          {
            "port": 80
          }
        ],
        "resources": {
          "limits": null,
          "requests": {
            "cpu": 1.0,
            "memoryInGb": 1.5
          }
        },
        "volumeMounts": null
      }
    ],
    "id": "/subscriptions/{subscriptionID}/resourceGroups/twxcontainers/providers/Microsoft.ContainerInstance/containerGroups/myname17810",
    "imageRegistryCredentials": [
      {
        "password": null,
        "server": "registry.hub.docker.com",
        "username": "joshualyon"
      }
    ],
    "ipAddress": null,
    "location": "eastus",
    "name": "myname17810",
    "osType": "Linux",
    "provisioningState": "Failed",
    "resourceGroup": "twxcontainers",
    "restartPolicy": null,
    "state": null,
    "tags": null,
    "type": "Microsoft.ContainerInstance/containerGroups",
    "volumes": null
  }
]

[seanmck]

Try index.docker.io for the registry-login-server.

[joshualyon]

Upon initial testing, index.docker.io seems to have worked for the registry-login-server. The container group and container both provisioned quickly and the application is running (albeit I have some port mapping to figure out).

Thanks for the assistance!