Skip to content
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

Issue with caching and build arguments #690

Closed
orf opened this issue Jun 4, 2019 · 0 comments · Fixed by #739
Closed

Issue with caching and build arguments #690

orf opened this issue Jun 4, 2019 · 0 comments · Fixed by #739
Labels
area/caching For all bugs related to cache issues

Comments

@orf
Copy link

orf commented Jun 4, 2019

Actual behavior
Building two images with differing build args results in incorrect images being built, when caching is enabled.

Expected behavior
Two individual images should be built

Reproduction
We have the following reduced Dockerfile:

FROM our_base_image
ARG python_version
RUN pyenv install ${PYTHON_VERSION}

If we build this Dockerfile with Kaniko:

kaniko/executor --build-arg PYTHON_VERSION=3.6 --destination=OUR_ECR_REGISTRY/python:3.6 --cache=true --cache-repo=OUR_ECR_REGISTRY/kaniko

and at the same time:

kaniko/executor --build-arg PYTHON_VERSION=3.7 --destination=OUR_ECR_REGISTRY/python:3.7 --cache=true --cache-repo=OUR_ECR_REGISTRY/kaniko

Then there appears to be some form of cache collision. The python:3.7 image has python 3.6 installed. To be clear: two different images are pushed.

We are using the latest kaniko docker image in Kubernetes. Could this be related to #639?

@orf orf mentioned this issue Jun 4, 2019
@priyawadhwa priyawadhwa added the area/caching For all bugs related to cache issues label Jul 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/caching For all bugs related to cache issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants