Hello, I have tried multiple things but the current version is the following: I have one Docker image containing node_modules. I want to COPY --from base --chown=node:node this base image node_modules directory into multiple other images. As this is the exact same node_modules directory I’m expe…

Just to confirm: could you create another base image which you can then use with FROM derived_base directly? If you could not, then I’d guess Docker is doing the expected thing, as apparently (if you could not rewrite for some FROM derived_base rather than COPY --from base) then the Nth layer is not…

@avbentem Thanks for your response. I can totally switch to using the base image without copying, I’m just trying to understand why a COPY --from is generating different layers. Sample Dockerfiles Base FROM node:lts-alpine RUN apk add --no-cache make g++ gcc python3 libc-dev libtool autoconf au…

So, you’re seeing the following creating a new layer in the final image for the COPY: [image] tirke: FROM node:lts-alpine ARG PROJECT ARG PORT=5000 RUN chmod g+rw /home && \ mkdir -p /home/node/app && \ chown -R node:node /home/node ENV HOME /home/node ENV NODE_ENV production WORKDIR /h…

[image] avbentem: And curious: did you try to use the image name in COPY --from <redacted>.amazonaws.com/baseimage:${BASETAG} ? Oh, if that gives you some “repository name must be lowercase” error, then that may be related to the (unresolved) How can I expand a variable within a COPY command …

I tried that and faced the same problem mentioned, it doesn’t work. But conceptually I don’t think it would be really different than using that. ARG BASETAG FROM <redacted>.amazonaws.com/baseimage:${BASETAG} AS deps And to be clear I’m more interested in pull cache than build cache but one goes wi…

[image] avbentem: As for COPY the documentation also mentions “metadata”, but I’ve no idea what that would refer to in your use case: If anything has changed in the file(s), such as the contents and metadata, then the cache is invalidated. It probably refers to this: root@ta-lxlt:/var/li…

COPY --from same source in different images produces a different layer

Docker Hub

avbentem (Arjan) December 29, 2021, 9:32pm 5

Oh, if that gives you some “repository name must be lowercase” error, then that may be related to the (unresolved) How can I expand a variable within a COPY command in the Dockerfile? (But that is digressing from your original problem; you could simply try with a hardcoded tag name instead.)

Topic		Replies	Views
Unexpected ADD and COPY behavior during build - Doesn't detect existing files General	6	5670	July 7, 2016
Using COPY to incremental copy files Docker Desktop windows	2	4407	October 9, 2018
Docker COPY/ADD no longer copies differences? General build	1	4739	March 5, 2018
How does --cache-from work with multiple images? General	3	14262	August 21, 2019
Same Dockerfile and build context, different layer digests General docker , build	7	3666	November 17, 2023

COPY --from same source in different images produces a different layer

Related topics