-
Notifications
You must be signed in to change notification settings - Fork 520
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
Dockerfile Linter doesn't recognize directory destination in COPY command #4292
Comments
For the backslash case, it's the challenge of interpreting quotes. As a workaround, if you put double backslashes the issue should go away. |
I'm not confident that your statement is correct. In the first line of the |
@SetTrend Thank you for pointing that out. You are correct that it does seem that the parser directive is not just for newlines at the end of a line in the file but also for content within the line. Sorry about that.
|
Perhaps you may want to follow this discussion on the /docker/docs/issues/19922: Dockerfile |
Thanks for the pointer. This does sound vaguely familiar... |
Synopsis
Although I correctly added a backslash to the destination of my
COPY
commands, the Dockerfile linter throws an error claiming that I didn't:Current Situation
The Dockerfile linter erroneously throws an error about a missing a trailing backslash although it has been provided.
Desired Situation
(For paths containing spaces, the array syntax is mandatory.)
ARG
,ENV
variables) should be correctly parsed and interpreted.VS Code Docker Extension Version
v1.29.0
Dockerfile Example Using Variables
The same
Dockerfile
as above, this time using variables for destination:The text was updated successfully, but these errors were encountered: