Skip to content

az containerapp up --registry-server fails when ACR has ABAC enabled #9724

Description

@pl4nty

Describe the bug

Same as microsoft/GitHub-Copilot-for-Azure#1106

Related command

az containerapp up --name myapp --source myapp --registry-server myacr.azurecr.io

Errors

The behavior of this command has been altered by the following extension: containerapp
Adding external ingress port 8080 based on dockerfile expose.
Using resource group 'myrg'
Using ContainerAppEnvironment 'mycae' in resource group myrg
Dockerfile detected. Running the build through ACR.
2026/03/26 01:08:46 Downloading source code...
2026/03/26 01:08:48 Finished downloading source code
when specifying push, at least one credential is required

Run ID: cr4 failed after 3s. Error: failed during run, err: exit status 1
Run failed

Issue script & Debug output

debug.txt

Expected behavior

Builds and pushes to the registry, then deploys

Environment Summary

azure-cli                         2.84.0

core                              2.84.0
telemetry                          1.1.0

Extensions:
containerapp                     1.3.0b4

Dependencies:
msal                            1.35.0b1
azure-mgmt-resource               24.0.0

Python location '/opt/az/bin/python3'
Config directory '/home/node/.azure'
Extensions directory '/home/node/.azure/cliextensions'

Python (Linux) 3.13.11 (main, Feb 25 2026, 02:29:30) [GCC 12.2.0]

Legal docs and information: aka.ms/AzureCliLegal


Your CLI is up-to-date.

Additional context

Debug log is sanitised, except for correlation IDs

Activity

  1. added
    bugThis issue requires a change to an existing behavior in the product in order to be resolved.
    on Mar 26, 2026
  2. added
    questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that
    customer-reportedIssues that are reported by GitHub users external to the Azure organization.
    Service AttentionThis issue is responsible by Azure service team.
    on Mar 26, 2026
  3. yonzhan commented on Mar 26, 2026

    @yonzhan
    Collaborator

    Thank you for opening this issue, we will look into it.

  4. removed
    questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that
    on Mar 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Auto-AssignAuto assign by botContainerAppService AttentionThis issue is responsible by Azure service team.bugThis issue requires a change to an existing behavior in the product in order to be resolved.customer-reportedIssues that are reported by GitHub users external to the Azure organization.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions