WalkerJ

According to this Github issue, there isn't a memory leak. Also see the top comment in the Reddit thread you linked to. Edit: After updating to the latest version of this container, it's reporting half the RAM usage it was previously. It's been running a couple of hours and has not increased. https://github.com/arvidn/libtorrent/issues/6667 Libtorrent started using memory mapped file IO which causes more memory to be reported as being used, but the additional "RAM" is actually virtual addresses used to access files more quickly. On Linux this uses mmap which has the effect of treating files like swap space. This makes file access faster because the application can read and write files one byte at a time as if it was RAM. It doesn't use any additional system RAM, but causes the OS to think the application is using RAM at those mapped addresses, even those the addresses are mapped to a file on disk, not an area in RAM. This can apparently cause some issues on Windows since it handles RAM and swap space differently than Unix type operating systems, but works as intended on Linux/Docker/Mac.

Can this container be used as the server/target for backing up clients? I want to back up my clients to my Unraid server. I previously had this working with Synology as the target, but the Synology Borgmatic app runs natively rather than in a container, so there's no Docker layer. The container doesn't appear to be configured with any port mappings by default. I tried adding a port mapping so I could SSH into the container but couldn't get it to work. I checked the permissions on the SSH folder and files without success. Can someone point me in the right direction?

Some of them were originally written by the same Docker containers that I'm trying to read them with now. I'm running a MusicBrainz Picard container from the Unraid app store, for example. I was using the Synology as storage for my Unraid server. The Synology shares were mounted through Unassigned devices. I tried converting the "language" using the -iconv parameter of rsync but it didn't change anything.

I am in the process of transferring my data from a Synology NAS to my Unraid server. I transferred all of the data and by chance noticed that I have some files on the Synology array that have special characters in the filename which when transferred to Unraid got converted to some other character. The character appears different depending on what OS I view it from. On MacOS it looks like a slash, in Krusader on Unraid it looks like a square with lines inside, and in Windows it looks like a character-sized rectangle. I'm not sure what it really is, but it's not what it was on the Synology file system. An example of where the special characters in file names came from is renaming music files with MusicBrainz Picard, but I have some other files that have special characters in names also. I've tried mounting the Synology shares as Unassigned Devices and copying the files with Krusader, transferring them with cp, mv, and rsync through SSH, and several other things - all with the same result. I've read every post and article on here and StackOverflow about rsync parameters and tried them all (--protect--args, -iconv, etc.) The end result is still the same. File system on Synology is BTRFS, Unraid is XFS. Is there a way to get these files from Synology to Unraid without the filenames being modified in the process?

Is it safe to move files into the .Recycle.Bin folder directly? For example, the DupeGuru duplicate file finding utility has an option to either delete duplicate files or move them to a "trash" folder somewhere. On my Synology NAS, I had it move them to the system trash folder, which worked fine. Would doing the same on Unraid, having DupeGuru move the files to be deleted to the .Recycle.Bin folder cause any problems?

Do you have any updates on this? Anything we can do to help?