Failed to deploy azure container with no incoming port due to MissingIpAddressPorts

Question

I'm attempting to deploy a container on a private subnet that doesn't require an incoming port but requires an IP for outbound connection (azure devops build agent) however it fails to deploy when no ports are provided. I don't understand why a port is required ? I shouldn't have to define a bogus port.

condensed ARM snippet:

    {
      "type": "Microsoft.ContainerInstance/containerGroups",
      "apiVersion": "2021-10-01",
      ...
      "properties": {
        "containers": [
          {
            ...
          }
        ],
        "subnetIds": [
          {
            "id": "...",
            "name": "ACI"
          }
        ],
        "osType": "Linux",
        "ipAddress": {
          "type": "Private",
          "ports": [
          ]
        }
      }

Error:

{"status":"Failed","error":{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"code":"BadRequest","message":"{
  \"error\": {
    \"code\": \"SubnetMissingRequiredDelegation\",
    \"message\": \"Subnet missing required delegation 'Microsoft.ContainerInstance' for container group 'buildagent-cache-server'.\"
  }
}"},{"code":"BadRequest","message":"{
  \"error\": {
    \"code\": \"MissingIpAddressPorts\",
    \"message\": \"The ports in the 'ipAddress' of container group 'buildagent-build-server0' cannot be empty.\"
  }
}"},{"code":"BadRequest","message":"{
  \"error\": {
    \"code\": \"MissingIpAddressPorts\",
    \"message\": \"The ports in the 'ipAddress' of container group 'buildagent-build-server1' cannot be empty.\"
  }
}"}]}}

Answer

As the type specified includes containerGroups also, - "type": "Microsoft.ContainerInstance/containerGroups", there should be a method that supports the container instances within the container group, can reach each other via localhost on any port, even if those ports aren't exposed externally on the group's IP address or from the container. That's the reason why the deployment fails. You should have to define a UDP port at least as a bogus port to address this.
Otherwise, you have to try the method involves Virtual Networks scenario as explains here: container-instances-virtual-network-concepts

----------

--please don't forget to upvote and Accept as answer if the reply is helpful--

Share via

Failed to deploy azure container with no incoming port due to MissingIpAddressPorts

1 answer