zeripath

Feel free, we can add watchdogsec to the service file if you like

Unfortunately you're just not giving us helpful information to solve this. We need logs. Add tracelogger to your configuration: ```ini [log] MODE= ..., traceldap ; ... [log.traceldap] MODE=file FILE_NAME=traceldap.txt LEVEL=trace...

are you sure that this is not already the case following #10803?

As far as I can see our entrypoint (for the docker with root) would ensure that the USER_UID is in the /etc/passwd file. Therefore I think this can only happen...

You need to update the repos involved to enable the PullRequests unit

@FrankCui-FengqiaoCui - please check your docker version. 1.17 is running alpine > 3.13 #18500 and docker versions less than 20.10.6 will break with hooks not running. @lihanglin - I need...

Ah so this is YET another duplicate of: https://github.com/go-gitea/gitea/issues/16428, https://github.com/go-gitea/gitea/pull/16451, https://github.com/go-gitea/gitea/pull/16170, https://github.com/go-gitea/gitea/issues/16464, https://github.com/go-gitea/gitea/issues/16484 See https://github.com/go-gitea/gitea/pull/18050 We put a huge warning in to tell people to upgrade their dockers for 1.17.

@99rgosse I don't understand your comment or how it's being reproduced.

> The bug could be reproduced when click the `update branch by rebase` in pull request UI. ~~AHA!~~ ~~That is the information I needed.~~ ~~I bet this update is not...

~~Right... ~~ ~~So the problem is likely:~~ https://github.com/go-gitea/gitea/blob/8430f738e296cd82f318744e2a9ddf74be27c353/services/pull/update.go#L68-L74 This ~~does not~~ directly causes an update the head refs which should also be being done as part of the post-receive hook....