devcontainers / devcontainers/cli
Unable to install the Azure CLI via features
- Langage dominant
- TypeScript
- Étoiles
- 3k
- Forks
- 457
- Merge moyen
- 13 h 17 min
- PR mergées (30 j)
- 6
Description
I'm using Podman Desktop 1.22 on Windows with a WSL v2 podman machine.
I started off using devcontainers inside vscode, but I'm getting the same error when using the devcontainers cli.
If I include the feature in my devcontainer.json:
```
"features": {
"ghcr.io/devcontainers/features/azure-cli:1": {}
}
```
I get this error when trying to build the container:
```
> devcontainer.cmd build --docker-path "C:\Program Files\RedHat\Podman\podman.exe" --workspace-folder .
[13 ms] @devcontainers/cli 0.80.1. Node.js v22.20.0. win32 10.0.26100 x64.
[1279 ms] Resolving Feature dependencies for 'ghcr.io/devcontainers/features/azure-cli:1'...
[2126 ms] Soft-dependency 'ghcr.io/devcontainers/features/common-utils' is not required. Removing from installation order...
[2445 ms] [httpOci] ERR: Server did not provide instructions to authentiate! (Required: A 'WWW-Authenticate' Header)
[2445 ms] Request failed
[2445 ms] (!) ERR: Failed to fetch feature: Failed to download package for ghcr.io/devcontainers/features/azure-cli
Error: Failed to download package for ghcr.io/devcontainers/features/azure-cli
at ZI (C:\Users\andomeda83\AppData\Local\nvm\v22.20.0\node_modules\@devcontainers\cli\dist\spec-node\devContainersSpecCLI.js:287:3957)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async KX (C:\Users\andomeda83\AppData\Local\nvm\v22.20.0\node_modules\@devcontainers\cli\dist\spec-node\devContainersSpecCLI.js:393:5401)
at async Pu (C:\Users\andomeda83\AppData\Local\nvm\v22.20.0\node_modules\@devcontainers\cli\dist\spec-node\devContainersSpecCLI.js:392:1995)
at async gC (C:\Users\andomeda83\AppData\Local\nvm\v22.20.0\node_modules\@devcontainers\cli\dist\spec-node\devContainersSpecCLI.js:395:2283)
at async Vu (C:\Users\andomeda83\AppData\Local\nvm\v22.20.0\node_modules\@devcontainers\cli\dist\spec-node\devContainersSpecCLI.js:395:282)
at async k7 (C:\Users\andomeda83\AppData\Local\nvm\v22.20.0\node_modules\@devcontainers\cli\dist\spec-node\devContainersSpecCLI.js:667:3505)
at async R7 (C:\Users\andomeda83\AppData\Local\nvm\v22.20.0\node_modules\@devcontainers\cli\dist\spec-node\devContainersSpecCLI.js:666:4937)
at async C:\Users\andomeda83\AppData\Local\nvm\v22.20.0\node_modules\@devcontainers\cli\dist\spec-node\devContainersSpecCLI.js:484:1188
{"outcome":"error","message":"Failed to download package for ghcr.io/devcontainers/features/azure-cli","description":"An error occurred building the container."}
```
I've tried authentication against ghrc.io via `podman login ghrc.io` and that doesn't make a difference.
Is there anything else I should try?
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Begin by reproducing the reported devcontainer CLI build with Podman on Windows and the Azure CLI feature, then compare the registry request and authentication behavior with a working runtime. Done means the feature downloads and the container build completes, with coverage for the reported missing WWW-Authenticate response if the project has an appropriate test location.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- typescript
- Domaine
- cli, devops
- Type d'issue
- Bug
- Difficulté
- 3/5
- Temps estimé
- 1-2 jours
- Activité
- À l'abandon
- Clarté
- À clarifier
- Accessibilité débutants
- 35/100