Gitlab deletes new branches instantly -> /home/git is not writable.

[opensourced]

My Gitlab Instance is behaving very strange. If I upload a new branch foo-branch containing some changes, then switch to Repository > Branches > foo-branch, Gitlab would give me a 404.

This behaviour however varies, sometimes i manage to open a Merge Request
and once the MR is open, it would show a error message, that this branch was not found and therefore the MR is invalid.

I just updated to version and i saw these lines in the log, that might be related. Is it possible that some permissions are not set up properly and therefore the data is written into the tmp directory where it is deleted after a short time?

On the VM I checked and the permissions for the app look correct.

...
Mar 29 06:47:58 `/home/git` is not writable.
Mar 29 06:47:58 Bundler will use `/tmp/bundler20230329-142-1f8zv0b142' as your home directory temporarily.
...

Is this a known issue?

[nebulon]

can you check if the app might run out of memory and thus keeps restarting in the background? Gitlab needs quite a lot of memory.

[girish]

@opensourced that warning comes from bundler and it can be ignored (it's not an error).

Are you able to see the issue on git.cloudron.io ?