Replies: 1 comment 1 reply
-
|
Hi 👋
Yes, that's expected as Features are always executed after the Dockerfile is executed.
Unfortunately, there is no current way to reverse the flow. However, how about adding the logic from your Dockerfiles to a lifecycle hook or to a local Feature? |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Thank you. I could not find any mention of the execution order in the docs. Could you point me to it please? |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
It seems that the basic feature I added to my dev container setup (common-utils) is only executed after the actual Dockerfile. This means I cannot use the non-root user the feature creates in my Dockerfile.
Is this a correct assumption? How can I change the execution order so the feature runs before the actual Dockerfile?
Beta Was this translation helpful? Give feedback.
All reactions