-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Absolute path passed as argument in docker-compose to Dockerfile becomes relative in linux #4849
Comments
It looks like the error is my fault. Per documentation:
Nonetheless I will have this issue remained open as the behavior seems inconsistent to me. |
What about this behavior is inconsistent? It's a security feature that prevents the Dockerfile to escape its build context and potentially damage your machine, or access sensitive data. |
Ah yes I totally get that. I should have clarified what I meant by "inconsistent behavior", and by that I mean the absolute -> relative path behavior. I surmise that this is simply an implementation detail. Though it would be better if the error is more on point when users are using paths outside the build context. |
I have the similar problem My requirement is that the jar is present in target directory of creditcard (mentioned in context) |
docker-compose.yml:
Dockerfile:
Docker compose version: 1.13.0, build 1719ceb
Docker version: 17.03.1-ce, build c6d412e
The text was updated successfully, but these errors were encountered: