Adding to @hufa's original fix by condensing the multiple chmod
commands into a single execution and chaining the call to the
setup script

Signed-off-by: Simon Deziel <simon@sdeziel.info>

MR: !4953

Balasankar 'Balu' C authored Feb 11, 2021 and DJ Mountney committed Feb 11, 2021

Also switch QA to use Ubuntu 20.04 artifacts
Signed-off-by: Balasankar "Balu" C <balasankarc@autistici.org>

As gitlab-ci checks out with mode 666 we need to set permissions of the
files we copied into the container to a secure value.

Fixes #5956

The reason is that some container systems don't run containers with
CAP_AUDIT_WRITE which is needed for pam. As the comment in sshd_config
has pointed out pam was used as a Fix because it handles shadow entries
'!' and '*' differently from ssh. This commit refixes that fix and
creates the git account with '*' (no password login) and disables pam in
sshd_config

Fixes #5891

timeout.

Using `patch` forces us to update the patch file everytime the config
file, or any other file mentioned in the patch is updated to accomodate
with the offset. Using sed to find-and-replace removes this requirement.

This will allow us to configure the healthcheck curl request
we make for containers from within the omnibus package.

Otherwise it may not be clear with port/url to reach the site on

This is in line with current Docker examples and avoids errors
due to lack of CAP_AUDIT_WRITE or some other error encountered
while setting the process attribute.

Such errors would manifest as error messages like the following:
PAM: pam_open_session(): Cannot make/remove an entry for the specified session

From https://docs.docker.com/engine/userguide/eng-image/dockerfile_best-practices/

Image shrunk from 365.2 -> 327.7 MB