Bug: Not all features from a collection are picked by the index
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- docker, github
- Domain
- build-system, devops
Research direction
Start by tracing the build process that produces the ghcr.io/devcontainers/index image and its devcontainer-index.json file. Compare the current and previous image contents, then inspect how the duplicated homebrew-package entry is handled for the devcontainers-extra collection. Done means the index contains the normal set of features and the containers.dev/features page lists them.
Written by the indexing model from the issue text.
Description
Today I noticed that there's only a single devcontainers-extra feature listed on https://containers.dev/features page (which is odd because all of them were listed previously)
I decided to check if it's reflected in ghcr.io/devcontainers/index container, and indeed I spotted that the latest image (sha256:67c13a273e686aee435df0ae312d367608716ed1a1c30fdc34bf18203733ac83) contains only one feature for devcontainer-extra entry:
While the previous image (sha256:5bbca131daff58a0ad98af37d527a0bd7c0c4e0c99bca4e9cb0b78fa34e3aa7e) contains the normal number of devcontainer-extra features:
The currently available feature is ghcr.io/devcontainers-extra/features/homebrew-package
On the devcontainers-extra container registry I can see that that feature is kind of doubled:
That's probably something I messed up, and as the result it messed up the process that is producing the index image with devcontainer-index.json file (so it only contains that single feature for devcontainers-extra collection)
Nevertheless, I don't know how that build process works, so I cannot check what exactly causes the issue and try to fix it (it was also mentioned in #480)
My only assumption is that it may be fixed when I remove doubled homebrew-package feature. Although the 1st image is namespaced with ghcr.io/devcontainers-extra, while the second is namespaced with ghcr.io/devcontainers-extra/features, so it still could be something else
@bamurtaugh is it possible to get more information about the build process of ghcr.io/devcontainers/index image? It may help to clarify what causes the issue, and maybe with fixing it
- Dominant language
- HTML
- Stars
- 207
- Forks
- 435
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from devcontainers/devcontainers.github.io
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Auto Assign workflow Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 42/100
devcontainers/devcontainers.github.io#693 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
D Open
Difficulty 5/5 Over a week Newbie friendliness 1/100
All issues in devcontainers/devcontainers.github.io
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
conda-forge/python-feedstock#934 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
bazelbuild/rules_rust#4266 ·
-
priority: p3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
googleapis/librarian#7636 ·
-
Bug v3
Difficulty 2/5 1-3 hours Newbie friendliness 86/100