Closed mlilien closed 4 years ago
Seems to be a local problem. The above error happens in arch linux with git 2.27.0. I tried to verify the problem with ubuntu 18.04 with git 2.17.1 and 2.27.0 and its not reproducable there. It seems to be a kind of routing problem. Thats odd though, because concourse and minio in the same bridged docker network are working as expected.
Reopening: I can reproduce this issue with a fresh vagrant arch linux box https://app.vagrantup.com/archlinux/boxes/archlinux
it is a permission problem: what fixed this issue in my dev env:
git init --bare myrepo.git
chmod -R g+w myrepo.git
umask
in ubuntu 18.04 is 0002
umask
in fedora 32 is 0002
umask
in arch is 0022
umask
in gentoo is 0022
What do we do? Adapt documentation? Or fix it in docker image?
In the image myrepo.git
belongs to 1000:1000
. The nginx server which needs group write permission is part of the group with gid 1000
.
If nginx has a configurable uid instead, we wouldnt have this permission problem, at least if we presume that the user who starts the server is the same which uses git commands later.
Since the image uses hardcoded uids/gids, we have to fix it anyway. Otherwise user with gid!=1000 will experience problems.
Good catch! Let's fork and fix this.
closed by removing git env