-
Notifications
You must be signed in to change notification settings - Fork 799
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
Add --parents option for COPY in Dockerfiles #5557
Comments
I believe @mheon is either working on this or looking into this. Matt? |
Yep, hoping to get to this over the next few weeks |
A friendly reminder that this issue had no activity for 30 days. |
This is so badly needed with Java projects that involve multiple |
any more update? |
bump this is a good idea |
any news? :) |
Could you give me a sample Containerfile that would use this? |
@rhatdan Of course. This sort of thing is useful in a workspace of any language where nested manifest files are involved. Here is an example in Rust (they are working on toolchain support for building only dependencies without project source, but that's not our concern). Alternatively, here is an example with Maven (which has existing toolchain support). To optimise layer caching, you would want something like this: COPY --parents **/pom.xml ./
RUN mvn dependency:go-offline Without |
https://github.com/larixer/docker-js-monorepo has some pretty good examples as well. |
Fixes: containers#5557 Signed-off-by: Daniel J Walsh <[email protected]>
Any news on this? it would be really helpful to have |
@Honny1 might have time to work on this? |
I will take a look. |
It also includes an implementation of the --parents flag for the buildah copy command. Fixes: https://issues.redhat.com/browse/RUN-2193 Fixes: containers#5557 Signed-off-by: Jan Rodák <[email protected]>
It also includes an implementation of the --parents flag for the buildah copy command. Fixes: https://issues.redhat.com/browse/RUN-2193 Fixes: containers#5557 Signed-off-by: Jan Rodák <[email protected]>
It also includes an implementation of the --parents flag for the buildah copy command. Fixes: https://issues.redhat.com/browse/RUN-2193 Fixes: containers#5557 Signed-off-by: Jan Rodák <[email protected]>
It also includes an implementation of the --parents flag for the buildah copy command. Fixes: https://issues.redhat.com/browse/RUN-2193 Fixes: containers#5557 Signed-off-by: Jan Rodák <[email protected]>
It also includes an implementation of the --parents flag for the buildah copy command. Fixes: https://issues.redhat.com/browse/RUN-2193 Fixes: containers#5557 Signed-off-by: Jan Rodák <[email protected]>
It also includes an implementation of the --parents flag for the buildah copy command. Fixes: https://issues.redhat.com/browse/RUN-2193 Fixes: containers#5557 Signed-off-by: Jan Rodák <[email protected]>
It also includes an implementation of the --parents flag for the buildah copy command. Fixes: https://issues.redhat.com/browse/RUN-2193 Fixes: containers#5557 Signed-off-by: Jan Rodák <[email protected]>
Description
Docker added a
--parents
option to the DockerfileCOPY
command last year:moby/moby#35639
moby/buildkit#3001
https://docs.docker.com/reference/dockerfile/#copy---parents
buildah doesn't know how to handle
COPY --parents
so errors out on Dockerfiles which use it.I'm seeing increasing use of
--parents
in Dockerfiles I have to deal with, which is making it hard to use podman/buildah instead of Docker.--parents
is also a genuinely useful option on its own, so would be nice to have not just for compatibility.It's quite useful to be able to do things like
and maintain the directory structure in the destination without having to list out every single file.
The text was updated successfully, but these errors were encountered: