devcontainers / devcontainers/cli

Error when devcontainer up

Ouverte
#849 3 commentaires 0 réactions 1 personne assignée Réclamée par @chrmarti Voir sur GitHub
bug
Langage dominant
TypeScript
Étoiles
3k
Forks
457
Merge moyen
13 h 17 min
PR mergées (30 j)
6

Description

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 ?

Guide de contribution

Ouvrir le guide de contribution

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.