Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

broken installsAfter on OCI repo

Open
#967 4 comments 0 reactions 1 assignee View on GitHub

@chrmarti is already working on this.

Since Mar 28, 2025.

Assessment

This issue has not been assessed yet.

Description

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
  ]
}
Dominant language
TypeScript
Stars
3k
Forks
461
Avg merge
18m
Merged PRs (30d)
5

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from devcontainers/cli

All issues in devcontainers/cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.