tree 1bb0b48e23e172ff815bca6952f009ba8a907d1c
parent bc026cf6961626dd01edfaf064562bfb1f2baf42
author Jarek Potiuk <jarek.potiuk@polidea.com> 1611089390 +0100
committer GitHub <noreply@github.com> 1611089390 +0100
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJgB0XuCRBK7hj4Ov3rIwAAdHIIAGOipy3X/ovKtgsbgBWyu4Le
 oXlNI6SPCCrOk40hAjGcGBfl3TdWgsm+UOQUTL3NvTo2w/WsqaK6zKJjldMyX9em
 Swrnrkk8deeTpfE7xeObHDzI6a+vq1Vul2Asm+MENfY8FbremApZaVPIZTSFHUux
 LEUo1XRdEOifEFvBIuKOjtxjAQZMCeiLzBRnhi0SRYDMXp1gRkl2gh38C+r0Nhzg
 ybW3lZG0kPifn9U6KGiUhFE6alXNgakX1YfBL8+yuL6FeuYPuPS10KjpUQsDOhW1
 /fN/w6vd1xFqJNqfzWqZaVmmllGwOMrI4/b4ram6vCZIliqSqD7bxtU1UYef7dM=
 =RaMS
 -----END PGP SIGNATURE-----
 

Remove chmod +x for installation script for docker build. (#13772)

We've introduced chmod a+x for installation scripts in Dockerfiles.
but this turned out to be a bad idea. This was to accomodate
building on Azure Deveops which has filesystem that does not
keep executable bit. But the side-effect of it that the
layer of the script is invalidated when the permission is changed
to +x on linux. The problem is that the script has locally (on
checkout) different permissions depending on umask setting.

Therefore changing permissions for the image to +a is not best.

Instead we are running the scripts with bash directly, which does
not require changing of executable bit.