Gitea installation - Permission denied

Apps and Virtualization
1

I try to install Gitea on TrueNAS Scale and created 5 datasets, gave “Apps” as “Share Type” and mounted it accordingly to Gitea:

/mnt/Tank/Gitea
/mnt/Tank/Gitea/data
/mnt/Tank/Gitea/config
/mnt/Tank/Gitea/db
/mnt/Tank/Gitea/dbbackup

Unfortunately the Gitea pod gives a permissions denied:

2024-04-12 12:35:27.986707-07:00 mkdir: can't create directory '/var/lib/gitea/git': Permission denied
2024-04-12 12:35:27.986793-07:00 /var/lib/gitea/git is not writable
2024-04-12 12:35:27.986848-07:00 docker setup failed

Any idea how to solve that problem?

Postgres Pod looks good. Unfortunately I cannot jump in the Gitea pod as it fails - so I can’t check UID or something…

2 Likes
2

Hi, I’m having the same issue. Have you found a solution/workaround?

1 Like
3

I am having the same issue when trying to install v1.22.1. Anyone have a solution?

4

@draescherl @phqzgunsfjror I have a few workarounds.

  1. Install in iXVolume dataset
  • This works without any unexpected modification to the Gitea app
  • The fact that we ran into the error described in this issue is due to using host paths rather than ixVolume, as far as I can tell
  • I’m not a fan of this because this dataset is unencrypted. If you want to use host path, use another method…
  1. Create a new dataset of preset Generic. Edit permissions and allow Write access for Group and Other. Install Gitea.
  • This works without any unexpected modification to the Gitea app
  • I’m not sure why this works or if this is a reasonable solution
  1. This is the method I went with:
  • Create a dataset with the Apps preset
  • Go to the system shell and create the 4 Gitea directories (data, configuration, postgres data, postgres backup)
  • Install Gitea: Specify the 4 directories under Storage Configuration, but with an unexpected tweak. For the data and configuration directories, enable ACL and grant user 1000 write access.

If you’re modifying an existing installation and this isn’t working, you might want to try a new one from scratch.

I have no idea why you need to grant user 1000 write access via ACL, but that is working for me. The app deployed correctly and I was able to finish the installation, reboot it, create a repo, and push to it. From what I can gather from other sources, user 1000 is internal to the container. I’m also not sure if this is the ideal solution or if it will survive future updates. If anyone has input or more detail on this, please share.

1 Like