Updog

I know it's been a while since this was made available, so I'm not certain this project is still active, but I'm watching the container log at the first run attempt and saw this interesting entry that gave me pause... (shredder:435): dconf-WARNING **: 14:38:58.020: failed to commit changes to dconf: Failed to execute child process “dbus-launch” (No such file or directory) This appears only after I modify and change settings in the search parameters / what to do with duplicates screen and click "apply". They don't look like they're saved, the log implies they aren't, and it looks like the choices I made don't end up being passed to rmlint in the way I'd hoped. I tried to search only files >1MB, but that gets reset when you navigate away from the page. I wanted to use hardlinks to recreate the previously hardlinked structure that was disrupted when I copied to a new disk with rsync. The hardlink option in the gui appears to still be selected, but that handler value, like the filesize filter, is not recorded and passed along as expected. In the end, instead of hardlinking my duplicates as I was expecting, it just removed them. I ran it on a relatively small directory for testing so the impact was really negligible, but for anything more substantial. Despite Hardlink being chosen, -c sh:handler=remove is set instead of -c sh:handler=hardlink. I've included a copy of the command that was ultimately run when turning off the dryrun toggle.

The umask is not set to unraid's expected 000 (or even 002) value in order to read/write these files, and defaults to the docker image's default 022. Some containers in unraid use the UMASK variable for docker containers to change this, but manually adding this parameter to the template doesn't result in the umask actually being set to 000 or 002 since it's not built into the app. According to https://codeyarns.com/tech/2017-07-21-how-to-set-umask-for-docker-container.html and https://forums.unraid.net/topic/32629-how-to-edit-a-dockerfile-locally/ the only way to go about this as-is would be to clone the MeTube repo locally, create a script which sets the umask to 000 when the container is run, then add that script in as the entrypoint of the local copy of the dockerfile. Doing this obviously keeps you from updating the container from its remote repo, which stinks, so the above solution seems unreasonably hacky. The current behavior is that the files created by MeTube are -rw-r--r-- when we'd hope they'd be -rw-rw-rw. We can't delete them or move them without hitting up the terminal on the unraid box itself to manually set perms as-is. If the maintainer could throw ENV UMASK 0000 into the startup script, I think we'd be in good shape. Other references: https://forums.unraid.net/topic/39289-adapting-container-user-and-group-ids-to-the-host/ https://forums.unraid.net/topic/32278-docker-container-developer-best-practice-guidelines-for-unraid/