-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Cannot stat: No such file or directory #362
Labels
kind/bug
Something isn't working
Comments
xanonid
added a commit
to xanonid/kaniko
that referenced
this issue
Sep 25, 2018
xanonid
added a commit
to xanonid/kaniko
that referenced
this issue
Sep 26, 2018
dlorenc
pushed a commit
that referenced
this issue
Sep 26, 2018
priyawadhwa
pushed a commit
to priyawadhwa/kaniko
that referenced
this issue
Nov 17, 2018
When we execute multistage builds, we store the fs of each intermediate stage at /kaniko/<stage number> if it's used later in the build. This created a bug when extracting hardlinks, because we weren't appending the new directory to the link path. So, if `/tmp/file1` and `/tmp/file2` were hardlinked, kaniko was trying to link `/kaniko/0/tmp/file1` to `/tmp/file2` instead of `/kaniko/0/tmp/file2`. This change will append the correct directory to the link, and fixes GoogleContainerTools#437 GoogleContainerTools#362 GoogleContainerTools#352 GoogleContainerTools#342.
priyawadhwa
pushed a commit
to priyawadhwa/kaniko
that referenced
this issue
Nov 17, 2018
When we execute multistage builds, we store the fs of each intermediate stage at /kaniko/<stage number> if it's used later in the build. This created a bug when extracting hardlinks, because we weren't appending the new directory to the link path. So, if `/tmp/file1` and `/tmp/file2` were hardlinked, kaniko was trying to link `/kaniko/0/tmp/file1` to `/tmp/file2` instead of `/kaniko/0/tmp/file2`. This change will append the correct directory to the link, and fixes GoogleContainerTools#437 GoogleContainerTools#362 GoogleContainerTools#352 GoogleContainerTools#342.
priyawadhwa
pushed a commit
to priyawadhwa/kaniko
that referenced
this issue
Nov 17, 2018
When we execute multistage builds, we store the fs of each intermediate stage at /kaniko/<stage number> if it's used later in the build. This created a bug when extracting hardlinks, because we weren't appending the new directory to the link path. So, if `/tmp/file1` and `/tmp/file2` were hardlinked, kaniko was trying to link `/kaniko/0/tmp/file1` to `/tmp/file2` instead of `/kaniko/0/tmp/file2`. This change will append the correct directory to the link, and fixes GoogleContainerTools#437 GoogleContainerTools#362 GoogleContainerTools#352 GoogleContainerTools#342.
sleepycat
added a commit
to cds-snc/report-a-cybercrime
that referenced
this issue
Jun 21, 2019
Kaniko builds a bit faster and simplifies cloudbuild config a little by automatically pushing images. Unfortunately it seems to build images that have missing files, which then causes breakage downstream. As an example: GoogleContainerTools/kaniko#362
sleepycat
added a commit
to cds-snc/report-a-cybercrime
that referenced
this issue
Jun 21, 2019
Kaniko builds a bit faster and simplifies cloudbuild config a little by automatically pushing images. Unfortunately it seems to build images that have missing files, which then causes breakage downstream. As an example: GoogleContainerTools/kaniko#362
sleepycat
added a commit
to cds-snc/report-a-cybercrime
that referenced
this issue
Jun 21, 2019
Kaniko builds a bit faster and simplifies cloudbuild config a little by automatically pushing images. Unfortunately it seems to build images that have missing files, which then causes breakage downstream. As an example: GoogleContainerTools/kaniko#362
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I tried to build Dockerfile (similar to this one) with Gitlab CI,
Actual result in current version
gcr.io/kaniko-project/executor:debug-8fb220b19b227bde9b7f4653da3b6b282be2fea4
and
gcr.io/kaniko-project/executor:debug-deda0ea04decceb8b758c764e6eeb9b8000e4095
Expected result as in version
gcr.io/kaniko-project/executor:debug-bb75c0461887034f40f5ba836cfd17647d2cf544
The text was updated successfully, but these errors were encountered: