Add features by Andrii Pravorskyi

[pravorskyi]

What type of PR is this?

• Add a new dev container collection
• Update to an existing dev container collection
• Documentation/spec update
• Other containers.dev site update (UX, layout, etc)

Related Issues

• Related Issue #
• Closes #

Description

Adds my dev container feature collection to the community index.

Collection checklist

If your PR contributes a new collection, please utilize this checklist:

• Collection name
• Maintainer name
• Maintainer contact link (i.e. link to a GitHub repo, email)
• Repository URL
• OCI Reference (must be the collection root, e.g. ghcr.io/<owner>/<repo> — one entry per repository, not one per Feature; do not include http:// or https://)
• I acknowledge that this collection provides new functionality, distinct from the existing collections part of this index.

[Kaniska (Kaniska244)]

Hi pravorskyi

The ociReference appears to be invalid and returning 404. Would you kindly check.

[pravorskyi]

Thanks for checking! It seems to me that reference is valid.
The 404 is a GitLab registry strict policy, it returns 404 for manifest requests that don't include the OCI Accept header (ghcr.io tolerates this, GitLab doesn't).

Spec-compliant clients pull it fine anonymously, e.g.:

oras pull registry.gitlab.com/pravorskyi/devcontainer-features:latest
# Downloaded c620bb2546ea devcontainer-collection.json

Could you check again, please?

[pravorskyi]

The devcontainer CLI sends the header GitLab requires. In the CLI's OCI client getManifest defaults to Accept: application/vnd.oci.image.manifest.v1+json.

https://github.com/devcontainers/cli/blob/main/src/spec-configuration/containerCollectionsOCI.ts#L315
https://github.com/devcontainers/cli/blob/main/src/spec-configuration/containerCollectionsOCI.ts#L522