Skip to content

Cannot create a Container Instance with multiple containers using YAML or Resource Manager template #27860

@chigivigi

Description

@chigivigi

Describe the bug

I cannot create a container instance with two docker containers using YAML or Resource Manager template described in microsoft documentation. The containers are inside an azure container registry.

When creating the container instance using ARM Template or YAML file i receive: The image 'myimage' in container group 'mygroup' is not accessible. Please check the image and azure registry credential.

Even when I use the registry username and registry password parameters in az container create command defined in my container registry Access keys I get the same error message.

The same command works if I define one image directly in command with the same username and password.

Related command

az container create --resource-group --name --image /: --cpu 1 --memory 1 --os-type Linux --ip-address public --registry-username --registry-password

az container create --resource-group myResourceGroup --file deploy-aci.yaml --registry-username --registry-password

az deployment group create --resource-group myResourceGroup --template-file azuredeploy.json

Errors

InaccessibleImage: The image 'myimage' in container group 'myinstance' is not accessible. Please check the image and registry credential.

Issue script & Debug output

InaccessibleImage: The image 'myimage' in container group 'myinstance' is not accessible. Please check the image and registry credential.

Expected behavior

The expected behavior should be the creation of a new container instance with two container that were defined inside YAML file or Resource Manager template file.

Environment Summary

azure-cli 2.54.0

core 2.54.0
telemetry 1.1.0

Dependencies:
msal 1.24.0b2
azure-mgmt-resource 23.1.0b2

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    ARMaz resource/group/lock/tag/deployment/policy/managementapp/account management-groupAuto-AssignAuto assign by botContainer Instancesaz containerService AttentionThis issue is responsible by Azure service team.act-identity-squadact-observability-squadcustomer-reportedIssues that are reported by GitHub users external to the Azure organization.questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions