Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

broken installsAfter on OCI repo

Abierto
#967 4 comentarios 0 reacciones 1 asignado Ver en GitHub

@chrmarti ya está trabajando en esto.

Desde el 28/3/2025.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

bug

Hi,

I have a devcontainer.json file referring to 2 features, feature Bar and feature Baz. The features are hosted in an OCI registry.
I am using vscode 1.97 and devcontainer extension 0.401.0

Feature Baz have an installAfter clause referring to feature Bar.
The container build fails when reference to feature Baz in feature B is not exactly the same (with version) as the one in the devcontainer.json.

VSCode tries to install feature Bar without a version and does not find it. If I put only the id of the feature instead of the full feature reference, it does not work either disregading what is specified in https://containers.dev/implementors/features/#installsAfter.

Here is a redacted version of the files:

{
  "image": "ubuntu:latest",
  "features": {
    "registry.gitlab.com/foo/bar:0.0.1": {},
    "registry.gitlab.com/foo/baz:0.0.1": {},
  }
}

feature bar:

{
  "name": "bar",
  "id": "bar",
  "version": "0.0.1",
}

feature baz not working:

{
  "name": "baz",
  "id": "baz",
  "version": "0.0.1",
  "installsAfter": [
    "registry.gitlab.com/foo/bar" => Does not work, VSCode tries to install the feature literally version without version does not exist
  ]
}

feature baz not working:

{
  "name": "baz",
  "id": "baz",
  "version": "0.0.1",
  "installsAfter": [
    "bar" => Does not work, VSCode does not see feature at all
  ]
}

feature baz working:

{
  "name": "baz",
  "id": "baz",
  "version": "0.0.1",
  "installsAfter": [
    "registry.gitlab.com/foo/bar:0.0.1" => works
  ]
}
Lenguaje dominante
TypeScript
Estrellas
3k
Forks
461
Merge medio
18 min
PR fusionados (30 d)
5

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de devcontainers/cli

Todos los issues de devcontainers/cli

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.