diff options
| author | Patrick Steinhardt <ps@pks.im> | 2020-02-19 11:34:55 +0100 |
|---|---|---|
| committer | Patrick Steinhardt <ps@pks.im> | 2020-02-19 11:34:55 +0100 |
| commit | 6efe3d358b7d3605d397d0c6fca8e6230a7995a9 (patch) | |
| tree | 909bbb54ff61d4d26d6690268049a8c08c66169a | |
| parent | 172239021f7ba04fe7327647b213799853a9eb89 (diff) | |
| download | libgit2-pks/coverity-fix-sudo.tar.gz | |
azure: docker: set up HOME variable to fix Coverity buildspks/coverity-fix-sudo
In commit 01a834066 (azure: docker: fix ARM builds by replacing gosu(1),
2020-02-18), we've switched our entrypoint from gosu(1) to use sudo(1)
instead to fix our ARM builds. The switch introduced an incompatibility
that now causes our Coverity builds to fail, as the "--preserve-env"
switch will also keep HOME at its current value. As a result, Coverity
now tries to set up its configuration directory in root's home
directory, which it naturally can't write to.
Fix the issue by adding the "--set-home" flag to sudo(1).
| -rw-r--r-- | azure-pipelines/docker/entrypoint.sh | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/azure-pipelines/docker/entrypoint.sh b/azure-pipelines/docker/entrypoint.sh index 830df49e9..8d96e3acd 100644 --- a/azure-pipelines/docker/entrypoint.sh +++ b/azure-pipelines/docker/entrypoint.sh @@ -1,4 +1,4 @@ #!/bin/bash -e useradd --shell /bin/bash libgit2 chown --recursive libgit2:libgit2 /home/libgit2 -exec sudo --preserve-env --user=libgit2 "$@" +exec sudo --preserve-env --set-home --user=libgit2 "$@" |