I've been trying to track down an issue where certain folders and files are having the owner changed to UNKOWN.

 

I first noticed the issue when using the tiredofit db-backup container to backup my mariadb Databases.

I was then trying to sync those backups to another server and I was getting permissions issues. Looking into this, I am able to set the permissions from within db-backup, but not PUID and PGID. So, I can manually set everything in the backup folder to owner: nobody, but as soon as a backup runs, all folders are set to UNKNOWN.

This hasn't been a huge issue since I could set the permissions to still allow the sync to run even if the owner wasn't what I'd like.

 

The next time I saw the issue was with Immich. I was getting intermittent permission errors in the logs when trying to auto-upload a photo. When I went to look in the Immich folders, the owner was set to UNKNOWN. Immich has the PUID and PGID set to 99 and 100. And when Immich creates a folder or file, it is set to nobody as would be expected.

But I have a container luckyBackup that syncs the Immich photos to another server. It would seem that each time this job ran, it changed the owner to UNKNOWN (I have yet to fully investigate luckyBackup as being the culprit - but it was disabled last night when it would normally have run a backup and the owner is still set correctly to nobody this morning).

 

So, being that I am a novice, what would you unRAID gurus do next to investigate what is causing this?

 

I have db-backup that seems to be doing this (and I can replicate the issue readily), but it has no access to Immich. So it can't be causing the problem there. Then I have luckyBackup. The folders is pulls from and backs up to all come out set to UNKNOWN. It was also syncing the DB backups, so I thought it was causing it everywhere until I ran the db-backup and realized it was doing it to the database backups on its own.

 

Is there some overall server setting that could be causing this? PUID and PGID seems to work fine 95% of the places they're set in containers. So it doesn't seem like the IDs are messed up. I'm grasping at straws here. 🙂

 

Thanks!

Happening to me too. Any resolution?

im seeing the something very similar with pihole, actually. its appdata config folder is owned by a user on my server that has never logged in (made an account for my wife to access some shares, she never bothered).

to test this i deleted the account and restarted pihole, and appdata config folder went from her user to UNKNOWN.

i tried setting --user 99:100 on the extra params for the container but then the container had start issues; i tried recursively setting the config folder to be owned by 99:100 (not the whole shared just theconfig, before people flip out), and uponc ontainer start, like clockwork, its reverted back to UNKNOWN owner.

im a bit at a loss here.

Edited January 24Jan 24 by hollowimage