VNet Configuration Not Applied to Azure Container Instances via Artillery `--overrides`

[abhutraxo]

Summary

When running Artillery distributed load tests using artillery run-aci with VNet/subnet configuration specified in aci-meta.json via the --overrides parameter, the containers are created without network configuration (no IP addresses, no subnet assignment).

Environment

• Artillery Version: 2.0.27
• Artillery Engine: artillery-engine-playwright@1.24.0
• Playwright Version: 1.57.0
• Subnet Delegation: ✅ Microsoft.ContainerInstance/containerGroups
• Service Principal Permissions: ✅ Network Contributor role assigned

Expected Behavior

Artillery containers should be deployed with:

• IP Type: Private
• IP Address: Assigned from subnet range
• Subnet ID: ...
• Network Profile: Valid network profile created/assigned

Actual Behavior

All containers are created with:

{
  "ipAddress": null,
  "subnetIds": null,
  "networkProfile": null,
  "provisioningState": "Succeeded"
}

Containers have no networking tab in Azure Portal and cannot communicate within the VNet.

Configuration Files

aci-meta.json (Current)

{
  "containerResources": {
    "cpu": 2,
    "memoryInGB": 4
  },
  "subnetIds": [
    {
      "id": "{Subnet details}"
    }
  ],
  "ipAddress": {
    "type": "Private"
  }
}

Artillery Command

artillery run-aci artillery/login-logout-flow.yml \
  --tenant-id $AZURE_TENANT_ID \
  --subscription-id $AZURE_SUBSCRIPTION_ID \
  --storage-account $STORAGE_ACCOUNT_NAME \
  --blob-container {Blob_container} \
  --resource-group {RG} \
  --region eastus2 \
  --count 5 \
  --overrides '{"containerResources":{"cpu":2,"memoryInGB":4},"subnetIds":[{"id":"/subscriptions/......(subnet details)"}],"ipAddress":{"type":"Private"}}' \
  --env-file .env.aci

We confirmed:

• ✅ Subnet delegation is correct
• ✅ Service Principal has sufficient permissions
• ✅ Subnet has available IP addresses
• ✅ Azure platform supports VNet integration in this configuration

Requested Information

To help troubleshoot, or how can I assign networking details to these contianers.

Labels: bug, azure, networking, vnet, aci, container-instances, documentation