change nobody:nobody to nobody:nogroup to be correct for Debian based image (#2189)

(for some reason, basic Kubernetes is able to run a Debian based container with nobody:nobody but
docker run and VMware WCP fail which should be expected behavior)

Signed-off-by: Dave Smith-Uchida <dsmithuchida@vmware.com>
pull/2206/head
David L. Smith-Uchida 2020-01-16 17:00:34 -08:00 committed by Steve Kriss
parent ee0cbcf11e
commit dcca3c3d2b
4 changed files with 4 additions and 4 deletions

View File

@ -28,6 +28,6 @@ RUN apt-get update && \
ADD /bin/linux/amd64/velero /velero
USER nobody:nobody
USER nobody:nogroup
ENTRYPOINT ["/velero"]

View File

@ -20,6 +20,6 @@ ADD /bin/linux/ppc64le/restic /usr/bin/restic
ADD /bin/linux/ppc64le/velero /velero
USER nobody:nobody
USER nobody:nogroup
ENTRYPOINT ["/velero"]

View File

@ -18,6 +18,6 @@ LABEL maintainer="Steve Kriss <krisss@vmware.com>"
ADD /bin/linux/amd64/velero-restic-restore-helper .
USER nobody:nobody
USER nobody:nogroup
ENTRYPOINT [ "/velero-restic-restore-helper" ]

View File

@ -18,6 +18,6 @@ LABEL maintainer="Prajyot Parab <prajyot.parab@ibm.com>"
ADD /bin/linux/ppc64le/velero-restic-restore-helper .
USER nobody:nobody
USER nobody:nogroup
ENTRYPOINT [ "/velero-restic-restore-helper" ]