exec /canipull: exec format error
- Dominant language
- Go
- Stars
- 5
- Forks
- 15
- Avg merge
- 3h 3m
- Merged PRs (30d)
- 1
Description
How to reproduce it.
1. Create AKS with user and system nodes as
Standard_D2ps_v6 and attach ACR(or dont attach, the result will be the same)
2. az login
3. az acr login --name
4. az aks get-credentials --resource-group --name
5. az aks check-acr --resource-group --name --acr --verbose --debug
As a resolt of command you will see
PS D:\dev\backend\infrastructure\k8s> az aks check-acr --resource-group development --name devaks --acr devacr.azurecr.io
Merged "devaks" as current context in C:\Users\User\AppData\Local\Temp\tmp3pmd7azx
cli.knack.cli: Event: CommandInvoker.OnTransformResult [, ]
cli.knack.cli: Event: CommandInvoker.OnFilterResult []
cli.knack.cli: Event: Cli.SuccessfulExecute []
cli.knack.cli: Event: Cli.PostExecute []
az_command_data_logger: exit code: 0
cli.__main__: Command ran in 3.931 seconds (init: 0.204, invoke: 3.727)
telemetry.main: Begin splitting cli events and extra events, total events: 1
telemetry.client: Accumulated 0 events. Flush the clients.
telemetry.main: Finish splitting cli events and extra events, cli events: 1
telemetry.save: Save telemetry record of length 3812 in cache file under C:\Users\User\.azure\telemetry\20250325110107323
telemetry.main: Begin creating telemetry upload process.
telemetry.process: Creating upload process: "C:\Program Files\Microsoft SDKs\Azure\CLI2\python.exe C:\Program Files\Microsoft SDKs\Azure\CLI2\Lib\site-packages\azure\cli\telemetry\__init__.pyc C:\Users\User\.azure C:\Users\User\.azure\telemetry\20250325110107323"
telemetry.process: Return from creating process 131792
telemetry.main: Finish creating telemetry upload process.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the failure with an AKS cluster using Standard_D2ps_v6 nodes, then run az aks check-acr with --verbose --debug as shown. Trace the exec format error to the diagnostic tool and verify that the command completes successfully on this node type without regressing the existing ACR health check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, go, kubernetes
- Domain
- cloud, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100