devcontainers / devcontainers/cli

Error when devcontainer up

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

描述

using 0.60 version of the cli i got :

```
No user features to update

TypeError: t.startsWith is not a function

at ytA (/usr/local/lib/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:465:2285)

at NH (/usr/local/lib/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:464:739)

at async KtA (/usr/local/lib/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:481:3692)

at async AB (/usr/local/lib/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:481:4807)

at async hrA (/usr/local/lib/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:661:13255)

at async lrA (/usr/local/lib/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:661:12996)

{"outcome":"error","message":"t.startsWith is not a function","description":"An error occurred setting up the container."}
```

The issue was reproduced in jenkins (where we have the CLI embedded there) but self resolved after a new pod created that runs the cli, (btw: no devcontainer.json changes happend in between) so i assume it is something related to caches or some files/data stored by the cli ?

贡献指南

打开贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

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