The file is here:

./var/lib/docker/volumes/ecbEDIT14c/_data/Fault Tolerant Tennis - Uploads from Fault Tolerant Tennis/3 Brilliant Alcaraz Tactics ANYONE Can Use (1080p_60fps_AV1-128kbit_AAC).mp4

a samba share with Windows is located at:

mnt/user/mdrive/

Is there a practical way to get file access to UNRAID apps files from my Windows PC ?

is it safe to set the docker settings Output directory to store files directly to: /mnt/user/mdrive/youtube/ ?

I had just left it blank

so the app itself had the download folder set as: /output

Is it safe to set the /mnt/user/mdrive share as the "output directory" ?

Here is a setup for a Docker container that I have running. You get to this by right clicking on the Docker icon:

Then select 'Edit':

Open up 'Show more settings'. You will have to add these three. The one circled is the one that is most confusing. First click on the 'EDIT' button.

The 'Container Path' is the path that where the Docker container would normally store any files that you want on the Unraid array. You enter that path under that. The 'Host Path' is where you want the files to actually be stored on the Unraid array/server. Obviously, it will be a User Share in virtually all cases.

As you can see, you work in the Docker container to set things up so that you don't have to looking for the files. With the proper setup and a bit of planning on your part, the files will be stored in a known location in a User Share.

(Since this is an SQL container, what is being stored on that Host Path is the SQL database. That database is being accessed via a port (3306) by a Kodi client computer to retrieve data via a SQL query. This means that the database within the appdata Share is never accessed as a regular share but it has to be stored on the array because it is so large that it requires physical storage space on a hard drive or a SSD. The appdata share is intended for exactly that type of use. )

Edited February 16Feb 16 by Frank1940
Grabbed the wrong screenshots the ffirst time.

The appdata for this app is below.

But I left the Output directory blank.

I added an appfiles share and I am going to put all my UNRAID docker files in there.

so I am going to use:

/mnt/user/appfiles/jdown

as the output directory.

Edited February 16Feb 16 by digitaldoctor

Is it safe to move files from

/var/lib/docker/volumes/ecbEDIT14c/_data/

to

/mnt/user/appfiles/jdown

?

Does this look good ?

mv -i * .. /mnt/user/appfiles/jdown

i am in the extremely long docker file right now. /var/lib/docker/volumes/ecbEDIT14c/_data/

this should move _data/ and all the content to my desired location.

-=-=-=-==-=-=-

Safe Procedure for Moving Data:

1. Stop the Container: docker stop <container_name>.

2. Move the Data: Use mv or rsync to move files from /var/lib/docker/volumes/ecbEDIT14c/_data/ to /mnt/user/appfiles/jdown.

3. Update Configuration: Update your Docker Compose file or docker run command to use -v /mnt/user/appfiles/jdown:/path/in/container instead of the old volume.

4. Restart the Container: Start the container to verify the files are recognized in the new location.

Key Considerations:

• Permissions: Moving files from /var/lib/docker (often root-owned) to /mnt/user (user share) might change file ownership or permissions, requiring a chown to the user the container runs as.

• Alternative: Instead of moving, using rsync -av allows you to copy data while keeping an archive, which is safer than mv.

-=-=-=-

mv * ..

Explanation and Usage

• mv: The command to move (or rename) files and directories.

• *: A wildcard character that the shell expands to match all files and directories in the current directory, except for hidden files (dotfiles, which start with a .).

• ..: A special reference that denotes the parent directory of your current location.

Important Considerations

• Overwriting: The mv command overwrites existing files in the destination without prompting by default, unless you use the -i (interactive) flag. It is a good practice to use mv -i to be prompted for confirmation before overwriting.

Edited February 16Feb 16 by digitaldoctor

I am not a Linux Guru. And mv is one of those dangerous Linux commands since it runs silently and, like many of the "two-letter" commands, it provides no warning when it is going to reek total havoc!

If moving the files is the only option, let me caution you to test the paths you are going to use.

Use the command to first verify every path:

ls -al

Its output will look like this:

Note that I have started from the root of the Linux file system with the full path name. Once you are sure you have the proper path name, use copy-and-paste operations to build the mv command.

1 hour ago, digitaldoctor said:

Does this look good ?

mv -i * .. /mnt/user/appfiles/jdown

i am in the extremely long docker file right now. /var/lib/docker/volumes/ecbEDIT14c/_data/

this should move _data/ and all the content to my desired location.

the move was successful.

I was unsure if my files would end up in

/mnt/user/appfiles/jdown/ or

/mnt/user/appfiles/jdown/_data/

It ended up in:

/mnt/user/appfiles/jdown/

(no _data)