Closed andyzhangx closed 3 years ago
/release-label-none
/release-label none
Why is this only relevant for the csi-driver-nfs? Can it break some other project when we merge this?
Why is this only relevant for the csi-driver-nfs? Can it break some other project when we merge this?
@pohly nfs Dockerfile add nfs package which is distro relevant, --build-arg a=b
just add a new arg for Dockerfile, if ARG a
does not exist in Dockerfile, it just ignore and won't break.
ARG ARCH
FROM k8s.gcr.io/build-image/debian-base-${ARCH}:v2.1.3
...
Add an ARCH in build arg is necessary since not all CSI drivers could use gcr.io/distroless/static:latest
base image since some CSI drivers needs to install some packages which is distro relevant
That explanation makes sense. Can you put it into the commit message?
That explanation makes sense. Can you put it into the commit message?
done, I set commit msg like this:
add build-arg ARCH for building multi-arch images, e.g. …
ARG ARCH
FROM k8s.gcr.io/build-image/debian-base-${ARCH}:v2.1.3
This is not how commit messages are normally written (https://chris.beams.io/posts/git-commit/), but okay.
/approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: andyzhangx, pohly
The full list of commands accepted by this bot can be found here.
The pull request process is described here
this PR is for https://github.com/kubernetes-csi/csi-driver-nfs/pull/166 to build multi-arch images original error:
https://prow.k8s.io/view/gcs/kubernetes-jenkins/logs/post-csi-driver-nfs-push-images/1363278699297771520
Does this PR introduce a user-facing change?: