[2.3.3] Docker: Can't install with postgres database folder pointing to a share #5370
Replies: 4 comments 5 replies
-
That doesn't have to do with folder or permissions. It's a networking error. Either the containers are not on the same network, DNS resolution isn't working, or perhaps the database isn't named db. |
Beta Was this translation helpful? Give feedback.
-
|
Hmm...it's a standard Debian 12 (no Desktop) linux container running on proxmox.
As mentioned before, the user has full write rights to this mount (and so in all subfolders too). I now have a running installation with media and data folder pointing to this share. I can scan and edit PDFs, so paperless is using this share. I even can create a file in the database folder: gamma@paperless-ngx:/mnt/paperless$ ls -la
total 1
drwxrwx--- 2 root lxc_shares 0 Jan 12 20:54 .
drwxr-xr-x 4 root root 4 Jan 5 15:20 ..
drwxrwx--- 2 root lxc_shares 0 Jan 12 22:05 data
drwxrwx--- 2 root lxc_shares 0 Jan 12 20:53 database
drwxrwx--- 2 root lxc_shares 0 Jan 12 21:36 media
drwxrwx--- 2 root lxc_shares 0 Jan 12 20:38 trash
gamma@paperless-ngx:/mnt/paperless$ ls -la database/
total 0
drwxrwx--- 2 root lxc_shares 0 Jan 12 20:53 .
drwxrwx--- 2 root lxc_shares 0 Jan 12 20:54 ..
gamma@paperless-ngx:/mnt/paperless$ touch database/test.txt
gamma@paperless-ngx:/mnt/paperless$ ls -la database
total 1
drwxrwx--- 2 root lxc_shares 0 Jan 12 22:31 .
drwxrwx--- 2 root lxc_shares 0 Jan 12 20:54 ..
-rwxrwx--- 1 root lxc_shares 0 Jan 12 22:31 test.txt
gamma@paperless-ngx:/mnt/paperless$ |
Beta Was this translation helpful? Give feedback.
-
|
Then I would look to the logs of your database container. If it has been stopped due to errors, that would also result in the name not being known. |
Beta Was this translation helpful? Give feedback.
-
|
The paperless compose file makes sure all containers are on the same network. The "cannot resolve host 'db'" could also mean the database container has not finished starting up. You can check this by looking at the postgres container logs. In my case it is the same permission error everyone else gets when first attempting networking share and mounting the database volume. The issue, at least for postgresdb, is the container hardcodes uid 999 when initializing. The created files permissions on the local mount must also carry over to the remote or the init phase gets permission errors. The SMB mount will also have to allow uid 999. The options I have seen so far:
|
Beta Was this translation helpful? Give feedback.
-
|
Also just ran into this problem. Error message is slightly different though: |
Beta Was this translation helpful? Give feedback.
-
|
try putting the db folder it its own share folder in the file server. Snippets of my compose yml & fstab. nfs server is synology |
Beta Was this translation helpful? Give feedback.
-
|
I have the same Problem, how do you fixed your problem? |
Beta Was this translation helpful? Give feedback.
-
|
I'm having the same bad luck. Looks like postgress (db-1) is not built to utilize the uid/gid mapping as the webserver and it locks permissions to only allow the postgres user (uid/gid 999) to read/write, etc. The solution for me is to create a separate mount for the db that is not in the same folder/share as the other mounted shares. |
Beta Was this translation helpful? Give feedback.
-
|
I bit my teeth out on this as well. My takeaway was that this is basically postgres signaling to me that it doesn't like to run on CIFS/SMB/NFS shares due to the risk of data loss. I read up a bit on soft vs. hard mounts (e.g. https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/What_are_the_differences_between_hard_mount_and_soft_mount), and then decided to have all folders locally and backup them to the network share separately. |
Beta Was this translation helpful? Give feedback.
-
I'm still playing with paperless-ngx. I had a test installation (docker) with default local path (except the consume folder, which pointed to a SMB share). Everything was fine.
For better backup and file access reasons, I wanted now to try to reinstall everything from scratch, but with all other path (media, data and database) also pointing to a SMB share.
It seems, media and data works, but the database path has an issue.
Here are my mount points:
/mnt/paperless/data
/mnt/paperless/media
/mnt/paperless/database
/mnt/paperless_consume (this is a share on another NAS)
The docker user has full rights to all these folders.
When installing with the docker installation script, I get the following output (and error at the end):
(When leaving the database folder as default, it works. So it's only affected to the db path.)
Beta Was this translation helpful? Give feedback.
All reactions