You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I use a Dockerfile in my build configuration, with a link specified, it does not trigger a link-dependency during startup.
It should, in my oppinion, be such that Dockerfile settings get parsed from the dockerfile and gets overridden by build-settings that in turn get overridden by run-settings.
Want me to look into a solution for this? I think this applies to more settings than just linking.
The text was updated successfully, but these errors were encountered:
You are right. Was porting from a fig-file and forgot that link is a Run-parameter and not a Build-parameter. Are compose-support planned? I would really like having as little dependency on maven config as possible (for increased portability).
If I use a Dockerfile in my build configuration, with a link specified, it does not trigger a link-dependency during startup.
It should, in my oppinion, be such that Dockerfile settings get parsed from the dockerfile and gets overridden by build-settings that in turn get overridden by run-settings.
Want me to look into a solution for this? I think this applies to more settings than just linking.
The text was updated successfully, but these errors were encountered: