checkout is owned by a different user inside the container

[junghans]

If the container runs as non-root user, the checkout might belows to a different user.

Example

name: CI
on: [push]
jobs:
  build:
    runs-on: ubuntu-latest
    container: votca/buildenv:latest
    steps:
      - uses: actions/checkout@master
        with:
          submodules: true
      - run: id
      - run: ls -l

The user is:

uid=1000(votca) gid=1000(votca) groups=1000(votca),10(wheel)

but the checkout is owned by uid 1001.

[junghans]

Ok, I got it, the checkout is done outside of the container and hence owned by 1001, adding options: --user 1001 to the container: block, seems like a good workaround.

[ethomson]

Glad you got this working - unfortunately, the docker containers can run as any user (as specified by the USER option in the Dockerfile) so there's very little control that we have over this. I'm going to close this issue, but if you have additional feedback, please see the GitHub Actions forum or contact us.

[junghans]

The problem is that the workaround above leads to other issues as the special user in the container had sudo rights, but of course, using a different user will not have that anymore.