-
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
symlink error building from jboss/base-jdk:8 #352
Labels
kind/bug
Something isn't working
Comments
Ooh, looks related to this commit, so perhaps it's fixed? |
@Bashton-MattBuckland , yah it looks like it should be solved by that commit! Could you give it a go with the latest version of the image ( |
I can confirm that #360 corrects the issue below... (I've tested it with one of my builds and it works fine now) INFO[0000] Downloading base image gcr.io/google-appengine/openjdk:8
INFO[0000] Mounted directories: [/kaniko /var/run /etc/mtab /proc /dev /dev/pts /sys /sys/fs/cgroup /sys/fs/cgroup/systemd /sys/fs/cgroup/cpuset /sys/fs/cgroup/blkio /sys/fs/cgroup/freezer /sys/fs/cgroup/cpu,cpuacct /sys/fs/cgroup/devices /sys/fs/cgroup/pids /sys/fs/cgroup/rdma /sys/fs/cgroup/memory /sys/fs/cgroup/net_cls,net_prio /sys/fs/cgroup/perf_event /sys/fs/cgroup/hugetlb /dev/mqueue /source /containers /dev/termination-log /etc/resolv.conf /etc/hostname /etc/hosts /dev/shm /run/secrets/kubernetes.io/serviceaccount /proc/bus /proc/fs /proc/irq /proc/sys /proc/sysrq-trigger /proc/kcore /proc/timer_list /sys/firmware]
INFO[0000] Extracting layer 0
error building image: error building stage: link /bin/gunzip /bin/uncompress: file exists |
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.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Actual behavior
When I run this:
I get this:
My
pwd
contains aDockerfile
with the following contents:I have also tried with
:latest
, but that gives up even sooner and gives me a usage error for some reason:Expected behavior
Run with no errors.
To Reproduce
Steps to reproduce the behavior:
Additional Information
See above
See above
For v0.3.0: sha256:6324339a98d9074e9edfdb1798a7768b10866e273c257706cb5290ddf24d82cc
For latest: sha256:42b4dd2a4651a300005bcaf23a0af74aaf25046c212f9c9556b4baeeda8985e5
The text was updated successfully, but these errors were encountered: