Open darkdragon-001 opened 2 years ago
Actual behavior
FROM
Expected behavior Cache should be based on content.
To Reproduce Create parent and child Dockerfiles, tag images accordingly and use cache.
Additional Information
FROM scratch as parent RUN echo "parent" > /identifier
ARG PARENT_TAG FROM parent:${PARENT_TAG} as child RUN cat /identifier
Kaniko Image: gcr.io/kaniko-project/executor:debug with sha256:3bc3f3a05f803cac29164ce12617a7be64931748c944f6c419565f500b65e8db
gcr.io/kaniko-project/executor:debug
sha256:3bc3f3a05f803cac29164ce12617a7be64931748c944f6c419565f500b65e8db
Triage Notes for the Maintainers
--cache
This is indeed not a good solution as it is right now.
Experiencing exactly same issue. Is there any workaround for this "FROM based on ARG" scenario?
Actual behavior
FROM
changed.FROM
is having the same sha but a different name/tagExpected behavior Cache should be based on content.
To Reproduce Create parent and child Dockerfiles, tag images accordingly and use cache.
Additional Information
Kaniko Image:
gcr.io/kaniko-project/executor:debug
withsha256:3bc3f3a05f803cac29164ce12617a7be64931748c944f6c419565f500b65e8db
Triage Notes for the Maintainers
--cache
flag