Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pull link information from Dockerfile #124

Closed
jburell opened this issue Mar 11, 2015 · 3 comments
Closed

Pull link information from Dockerfile #124

jburell opened this issue Mar 11, 2015 · 3 comments

Comments

@jburell
Copy link

jburell commented Mar 11, 2015

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.

@jgangemi
Copy link
Collaborator

can you post an example of such a Dockerfile? is this fig/compose related (which is not yet supported and probably a larger discussion)?

@jburell
Copy link
Author

jburell commented Mar 12, 2015

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).

@rhuss
Copy link
Collaborator

rhuss commented Mar 12, 2015

Yes, compose support is planned (see #57). Closing this this ticket, feel free to reopen it if you still need support here.

@rhuss rhuss closed this as completed Mar 12, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants