Use 'chmod a-x' instead of 'chmod -x'
There is a subtle difference when executable bit is a part of the umask. And at least some versions (Debian/stretch) fail if the resulting mode would've been different if not for the umask setting. Fixes #998. Although, with such chmods/umasks it is likely that some package installation will break anyway. But I'll leave it until somebody complains. Signed-off-by: Alexey Neyman <stilor@att.net>dev-linux
parent
29f0662c18
commit
d573c15758
@ -1,3 +1,3 @@
|
||||
FROM hoverbear/archlinux
|
||||
FROM base/archlinux:latest
|
||||
RUN pacman -Syu --noconfirm
|
||||
RUN pacman -S --noconfirm base-devel git help2man python unzip
|
||||
|
@ -1,4 +1,4 @@
|
||||
FROM gentoo/stage3-amd64-hardened
|
||||
RUN wget -O /sbin/dumb-init https://github.com/Yelp/dumb-init/releases/download/v1.2.1/dumb-init_1.2.1_amd64
|
||||
RUN chmod +x /sbin/dumb-init
|
||||
RUN chmod a+x /sbin/dumb-init
|
||||
ENTRYPOINT [ "/sbin/dumb-init", "--" ]
|
||||
|
Loading…
Reference in New Issue