Install a feature after all features

[yf-yang]

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

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?

[PmPPolska]

pt., 13 gru 2024, 06:39 użytkownik yf-yang ***@***.***> napisał:

…

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? — Reply to this email directly, view it on GitHub <#524>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BDJKZVCCB6PCIRZM5KU3VST2FJXJ7AVCNFSM6AAAAABTRIHT4OVHI2DSMVQWIX3LMV43ASLTON2WKOZSG4ZTONBVGI4TEMA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[bamurtaugh]

Thanks for opening! Does the info in https://containers.dev/implementors/features/#installation-order help with the scenarios you had in mind?

[yf-yang]

@bamurtaugh I've already checked the doc.

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

If I got it right, as long as I create a feature and reference it with relative path, it will always be invoked before ghcr.io official features?