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
While working on a JS/TS Dockerfile generator, I came across some inconsistencies in how the RUN mount options are being parsed/handled.
I just opened an issue for the documentation, but checking the sources, it looks like this might be more source related.
Examples:
## Works with all options that are not listed as supportedRUN --mount=type=tmpfs,target=/cache,size=1024,ro,readonly,rw,readwrite /bin/ls -asl /cache
## Not listed as supported, but pulls from registry## ERROR [internal] load metadata for docker.io/library/nonexistent:latestRUN --mount=type=tmpfs,target=/cache,size=1024,from=nonexistent /bin/ls -asl /cache
## Shows directories in root, documentation says from=<stage>, but happily loads imageRUN --mount=type=cache,target=/cache,from=alpine:3,source=/ /bin/ls -asl /cache
I'm not sure if I'm proficient enough in Go to actually come up with a good solution for this and I couldn't find any specs for what the correct behaviour should be, but I believe that the problem lies in parseMount in commands_runmount.go
Happy weekend!
The text was updated successfully, but these errors were encountered:
from= takes the same argument as FROM <base> or COPY --from=<stage>. It can be named build context, named stage or image name, in that order or preference.
While working on a JS/TS Dockerfile generator, I came across some inconsistencies in how the RUN mount options are being parsed/handled.
I just opened an issue for the documentation, but checking the sources, it looks like this might be more source related.
Examples:
I'm not sure if I'm proficient enough in Go to actually come up with a good solution for this and I couldn't find any specs for what the correct behaviour should be, but I believe that the problem lies in
parseMount
incommands_runmount.go
Happy weekend!
The text was updated successfully, but these errors were encountered: