1. 19 Feb, 2020 1 commit
    • azure: docker: set up HOME variable to fix Coverity builds · 6efe3d35
      In commit 01a83406 (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).
      Patrick Steinhardt committed
  2. 18 Feb, 2020 1 commit
    • azure: docker: fix ARM builds by replacing gosu(1) · 01a83406
      Our nightly builds are currently failing due to our ARM-based jobs.
      These jobs crash immediately when entering the Docker container with a
      exception thrown by Go's language runtime. As we're able to successfully
      builds the Docker images in previous steps, it's unlikely to be a bug in
      Docker itself. Instead, this exception is thrown by gosu(1), which is a
      Go-based utility to drop privileges and run by our entrypoint.
      
      Fix the issue by dropping gosu(1) in favor of sudo(1).
      Patrick Steinhardt committed
  3. 07 Feb, 2020 1 commit
    • azure: docker: avoid re-creating libgit2 home directory · fb03f02a
      The Docker entrypoint currently creates the libgit2 user with "useradd
      --create-home". As we start the Docker container with two volumes
      pointing into "/home/libgit2/", the home directory will already exist.
      While useradd(1) copes with this just fine, it will print error messages
      to stderr which end up as failures in our Azure pipelines.
      
      Fix this by simply removing the "--create-home" parameter.
      Patrick Steinhardt committed
  4. 21 Sep, 2019 1 commit
    • azure: avoid building and testing in Docker as root · 3c884cc3
      Right now, all tests in libgit2's CI are being executed as root
      user. As libgit2 will usually not run as a root user in "normal"
      usecases and furthermore as there are tests that rely on the
      ability to _not_ be able to create certain paths, let's instead
      create an unprivileged user "libgit2" and use that across all
      docker images.
      Patrick Steinhardt committed