tar chown issues with nfs backed volume

[mprovenz]

Hi there, having issues using the container with an nfs backed volume for the data storage. The photon DB downloads properly, but tar generates errors when running.

2025-06-17 14:05:21 (4.31 MB/s) - ‘/photon/photon_data/temp/photon-db.tar.bz2’ saved [21775632136/21775632136] photon-db.tar.bz2: OK [INFO] 2025-06-17 14:08:08 - MD5 verification successful [INFO] 2025-06-17 14:08:08 - Extracting archive, this may take some time... [INFO] 2025-06-17 14:08:08 - Extracting archive to /photon/photon_data/temp tar: photon_data/node_1/logs/photon_server.json: Cannot change ownership to uid 998, gid 998: Operation not permitted ....

If I am understanding correctly, I believe the issue is that tar is attempting to restore the original owner/group on the files when extracting which is getting rejected by my NFS server due to those IDs not existing. It seems as if specifying the tar options '--no-same-permissions' and '--no-same-owner' would solve this issue for me and others with a similar setup.

If I am not interpreting this correctly please let me know!

Thanks!

[rtuszik]

Thank you for putting me on to this! I definitely think that this is a permissions issue. I made a few changes with regards to how the files are ran and accessed.

There is now an option to set the PUID and PGID of the user on the host system in order to allow it to access the files.

Are you able to check if this works for you?

The updated images is available at rtuszik/photon-docker:dev

[max2697]

I'm experiencing the same issue with version 0.7.0-rev.4:

photon-db.tar.bz2: OK
[INFO] 2025-06-24 01:22:27 - MD5 verification successful
[INFO] 2025-06-24 01:22:27 - Extracting archive, this may take some time...
[INFO] 2025-06-24 01:22:27 - Extracting archive to /photon/photon_data/temp
tar: photon_data/node_1/logs: Cannot change mode to rwxr-xr-x: Bad address

[mprovenz]

Thank you for putting me on to this! I definitely think that this is a permissions issue. I made a few changes with regards to how the files are ran and accessed.

There is now an option to set the PUID and PGID of the user on the host system in order to allow it to access the files.

Are you able to check if this works for you?

The updated images is available at rtuszik/photon-docker:dev

Appreciate the looking into this - I will give it a shot this week and let you know! Thanks again!

[max2697]

I tested the dev version and still have the same issues:

• I verified the user ID and group ID, and added them to the Docker Compose file.
• I saw the logs showing GID and UID being updated when the app starts.
• But I’m still getting these errors:

photon-db.tar.bz2: OK
[INFO] 2025-06-24 02:11:05 - MD5 verification successful
[INFO] 2025-06-24 02:11:05 - Extracting archive, this may take some time...
[INFO] 2025-06-24 02:11:05 - Extracting archive to /photon/photon_data/temp
tar: photon_data/node_1/data/nodes/0/indices/fSf5YANCRWaencCdSdnQWQ/0/index: Cannot change mode to rwxr-xr-x: Bad address
tar: photon_data/node_1/data/nodes/0/indices/fSf5YANCRWaencCdSdnQWQ/0/translog: Cannot change mode to rwxr-xr-x: Bad address
tar: photon_data/node_1/data/nodes/0/indices/fSf5YANCRWaencCdSdnQWQ/0/_state: Cannot change mode to rwxr-xr-x: Bad address
tar: photon_data/node_1/data/nodes/0/indices/fSf5YANCRWaencCdSdnQWQ/0: Cannot change mode to rwxr-xr-x: Bad address

UPD: I removed all folders and manually created the photon_data folder on the host using my user’s GID and UID.
Then I ran the Docker container—but it’s still creating files inside that folder with GID and UID 0, not the values I set.

[RodoMa92]

Yeah, just tested the same image on my end and it still tries to change permission to the wrong user (on my end is 998). Solved by not using a nfs shared storage space, for now; since there is no user data in this image.

[rtuszik]

I have been able to replicate this issue and I'm working on a fix right now. I'll keep you posted.