I updated a Gitea instance (1.18.5) to 1.19 today, but it won’t start. I run it in Kubernetes, so I get pod “completed”, and then backoff.
Here are the logs:
Server listening on :: port 22.
Server listening on 0.0.0.0 port 22.
2023/03/21 17:42:03 cmd/web.go:105:runWeb() [I] Starting Gitea on PID: 19
2023/03/21 17:42:03 …s/setting/setting.go:322:loadRunModeFrom() [F] Expect user ‘gitea’ but current user is: git
In my config, I set the RUN_USER to git (was gitea), and this seems to fix the problem.
RUN_USER = git
I don’t see anything in the release notes about it. I’m not sure if I had an improper config fore.
As you noted, RUN_USER is the user running Gitea.
In our docs we usually recommend git, but I’m curious what would have set it before this update and why it was changed.
Technically the user can be anything so long as it matches, which is why I find it odd that something would have altered it.
Do you have any more information about your setup that may be relevant?
cmd/web.go:105:runWeb() [I] Starting Gitea on PID: 7
…s/setting/setting.go:322:loadRunModeFrom() [F] Expect user ‘git’ but current user is:
Your error message looks like there is no user with uid 1002 on your system. Can you run command id 1002 and show what it responds? Also what version of Docker server are you running (check with docker --version)?