devcontainers / devcontainers/cli

Unable to install the Azure CLI via features

未关闭
#1,096 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
主要语言
TypeScript
星标
3k
派生
457
平均合并
13 小时 17 分钟
30 天内合并 PR
6

描述

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?

贡献指南

打开贡献指南

调研方向

首先,使用 Windows 上的 Podman 和 Azure CLI feature 重现报告的 devcontainer CLI 构建,然后将 registry 请求和身份验证行为与正常工作的运行时进行比较。完成标准是 feature 能够下载并且容器构建完成;如果项目有合适的测试位置,还应覆盖报告的缺失 WWW-Authenticate 响应。

由索引模型根据 Issue 内容生成。

评估

技术栈
typescript
领域
cli, devops
Issue 类型
缺陷
难度
3/5
预计耗时
1-2 天
活跃度
停滞
描述清晰度
需要澄清
新手友好度
35/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。