devcontainers / devcontainers/spec
Install a feature after all features
- Dominant language
- No language data
- Stars
- 5.7k
- Forks
- 496
- PR merge metrics
- No merged PRs in 30d
Description
Use case: I'd like to install some packages when building the container, so I wrote a Dockerfile. However, the Dockerfile is always executed before the features, so whenever I change the packages installed in the Dockerfile, the whole building process won't benefit from the cache.
Therefore, I tried to write a new feature to do that. However, then I found that the new feature is always executed first (maybe that's because path like "./features/xxx" is always executed before "ghcr.io/xxx". (I don't quite understand if that's the [fully qualified name](https://containers.dev/implementors/features/#definition-feature-equality)
Anyway, is there a way that I can force the feature to be executed at the end, such as explicitly set roundPriority? Or are there any alternatives to do so?
Contributor guide
Assessment
This issue has not been assessed yet.