/home/nobody/Downloads

 

Where is this and how can I get to it? I have been trying to use delugevpn and it is not working right and it seems to be downloading the file to that path and i want to make sure that the files are no longer there so they aren't taking up space.

It's in RAM so a reboot will delete it.

 

It's in RAM so a reboot will delete it.

okay, any ideas why it keeps going there but when i try to move it to my disk it does nothing? This is how i have it set up

/home/nobody/Downloads

 

Where is this and how can I get to it? I have been trying to use delugevpn and it is not working right and it seems to be downloading the file to that path and i want to make sure that the files are no longer there so they aren't taking up space.

This path is inside the docker image file, easiest way to clean it out is to delete the docker image file and reinstall your dockers from the my_ templates.

 

If you really want to dig into the image manually, telnet or ssh into your tower and run

docker exec -it binhex-delugevpn bash

which will drop you to a prompt inside the container. Then you can cd into the folder and delete any rogue downloads. Be careful, as the container has some legitimate content inside the nobody folder, so don't just kill everything in there.

/home/nobody/Downloads

 

Where is this and how can I get to it? I have been trying to use delugevpn and it is not working right and it seems to be downloading the file to that path and i want to make sure that the files are no longer there so they aren't taking up space.

This path is inside the docker image file, easiest way to clean it out is to delete the docker image file and reinstall your dockers from the my_ templates.

 

If you really want to dig into the image manually, telnet or ssh into your tower and run

docker exec -it binhex-delugevpn bash

which will drop you to a prompt inside the container. Then you can cd into the folder and delete any rogue downloads. Be careful, as the container has some legitimate content inside the nobody folder, so don't just kill everything in there.

honestly I'm new to linux and command line but that seems easy enough so I'll try it after i figure out how to get my torrents to actually go to my disks rather than the nobody folder so i don't have to keep going back lol

This is how i have it set up

This is totally wrong, but without seeing your docker folder mapping, it's impossible to tell you how to fix it. Post a screenshot of the docker setup for this container.

This is how i have it set up

This is totally wrong, but without seeing your docker folder mapping, it's impossible to tell you how to fix it. Post a screenshot of the docker setup for this container.

it should be in that imgur album

This is how i have it set up

This is totally wrong, but without seeing your docker folder mapping, it's impossible to tell you how to fix it. Post a screenshot of the docker setup for this container.

it should be in that imgur album

You are right, it was, but the black background hid it from me. You need to set the "Download to:" field to /data, because that's what you have set as the mapped folder. Any subfolders that you set up in the other fields need to have /data as the root of the path.

This is how i have it set up

This is totally wrong, but without seeing your docker folder mapping, it's impossible to tell you how to fix it. Post a screenshot of the docker setup for this container.

it should be in that imgur album

You are right, it was, but the black background hid it from me. You need to set the "Download to:" field to /data, because that's what you have set as the mapped folder. Any subfolders that you set up in the other fields need to have /data as the root of the path.

okay, I'm somewhat following i think. So is the only thing that i need to change is the "download to" field?

 

Should i change it so that it downloads it to my user/media/... in case i add more disks? I just have it going to disk1/Media/... because i was trying to figure out what was going on

BTW, the correct place for your post would have been in the support thread for the specific docker you are asking about, http://lime-technology.com/forum/index.php?topic=45812.0

 

BTW, the correct place for your post would have been in the support thread for the specific docker you are asking about, http://lime-technology.com/forum/index.php?topic=45812.0

yeah, i mostly wanted to know where the nobody folder was but then it turned into deluge...

okay, I'm somewhat following i think. So is the only thing that i need to change is the "download to" field?

 

Should i change it so that it downloads it to my user/media/... in case i add more disks? I just have it going to disk1/Media/... because i was trying to figure out what was going on

You need to change any path that you want deluge to be able to use to one that references /data. If you want your completed downloads to go to media/completed, then you need to change completed to /data/completed. The mapping is a direct 1 for 1 substitution for what you want the docker to do.

 

In general, if you want a folder to use multiple drives, yes, you use /mnt/user/sharename instead of /mnt/disk1/sharename.

 

Have you read the wiki on how shares work?

BTW, the correct place for your post would have been in the support thread for the specific docker you are asking about, http://lime-technology.com/forum/index.php?topic=45812.0

yeah, i mostly wanted to know where the nobody folder was but then it turned into deluge...

The nobody folder you were referencing only exists inside the deluge docker container. You can't get to it from anywhere else.

okay, I'm somewhat following i think. So is the only thing that i need to change is the "download to" field?

 

Should i change it so that it downloads it to my user/media/... in case i add more disks? I just have it going to disk1/Media/... because i was trying to figure out what was going on

You need to change any path that you want deluge to be able to use to one that references /data. If you want your completed downloads to go to media/completed, then you need to change completed to /data/completed. The mapping is a direct 1 for 1 substitution for what you want the docker to do.

 

In general, if you want a folder to use multiple drives, yes, you use /mnt/user/sharename instead of /mnt/disk1/sharename.

 

Have you read the wiki on how shares work?

i think i did but not certain to be honest.I mean I know that i should use mnt/user/... to point towards all of my drives. I just didn't know about the /data/completed etc.

This is how i have it set up

This is totally wrong, but without seeing your docker folder mapping, it's impossible to tell you how to fix it. Post a screenshot of the docker setup for this container.

it should be in that imgur album

You are right, it was, but the black background hid it from me. You need to set the "Download to:" field to /data, because that's what you have set as the mapped folder. Any subfolders that you set up in the other fields need to have /data as the root of the path.

okay, I'm somewhat following i think. So is the only thing that i need to change is the "download to" field?

 

Should i change it so that it downloads it to my user/media/... in case i add more disks? I just have it going to disk1/Media/... because i was trying to figure out what was going on

The key point to realise is that the first screenshot shows the paths as seen INSIDE the container and are not visible at the host level.  These will be equivalent to the values in the Container Volume field when setting up mapping.  You want to make sure that each path is mapped to a Host Path that is somewhere on your unRAID system.  Any container path that is not mapped properly to a host path will result in files being written inside the container - something you definitely do not want as it would fill up the docker.img file holding the container binaries.  Note that you can change these mapping entries at any time by Editing the Container properties (while it is stopped) so it is not critical that you get them perfectly right initially as long as they are all mapped to locations outside the docker container.

 

This is how i have it set up

This is totally wrong, but without seeing your docker folder mapping, it's impossible to tell you how to fix it. Post a screenshot of the docker setup for this container.

it should be in that imgur album

You are right, it was, but the black background hid it from me. You need to set the "Download to:" field to /data, because that's what you have set as the mapped folder. Any subfolders that you set up in the other fields need to have /data as the root of the path.

okay, I'm somewhat following i think. So is the only thing that i need to change is the "download to" field?

 

Should i change it so that it downloads it to my user/media/... in case i add more disks? I just have it going to disk1/Media/... because i was trying to figure out what was going on

The key point to realise is that the first screenshot shows the paths as seen INSIDE the container and are not visible at the host level.  These will be equivalent to the values in the Container Volume field when setting up mapping.  You want to make sure that each path is mapped to a Host Path that is somewhere on your unRAID system.  Any container path that is not mapped properly to a host path will result in files being written inside the container - something you definitely do not want as it would fill up the docker.img file holding the container binaries.  Note that you can change these mapping entries at any time by Editing the Container properties (while it is stopped) so it is not critical that you get them perfectly right initially as long as they are all mapped to locations outside the docker container.

okay, I think I understand now (I hope).

 

So technically /data = /mnt/user/Media/... Correct? So if I point to /data inside of Deluge or whatever other docker it will put the files in /mnt/user/Media/... because they are the same location(?)

 

This is how i have it set up

This is totally wrong, but without seeing your docker folder mapping, it's impossible to tell you how to fix it. Post a screenshot of the docker setup for this container.

it should be in that imgur album

You are right, it was, but the black background hid it from me. You need to set the "Download to:" field to /data, because that's what you have set as the mapped folder. Any subfolders that you set up in the other fields need to have /data as the root of the path.

okay, I'm somewhat following i think. So is the only thing that i need to change is the "download to" field?

 

Should i change it so that it downloads it to my user/media/... in case i add more disks? I just have it going to disk1/Media/... because i was trying to figure out what was going on

The key point to realise is that the first screenshot shows the paths as seen INSIDE the container and are not visible at the host level.  These will be equivalent to the values in the Container Volume field when setting up mapping.  You want to make sure that each path is mapped to a Host Path that is somewhere on your unRAID system.  Any container path that is not mapped properly to a host path will result in files being written inside the container - something you definitely do not want as it would fill up the docker.img file holding the container binaries.  Note that you can change these mapping entries at any time by Editing the Container properties (while it is stopped) so it is not critical that you get them perfectly right initially as long as they are all mapped to locations outside the docker container.

okay, I think I understand now (I hope).

 

So technically /data = /mnt/user/Media/... Correct? So if I point to /data inside of Deluge or whatever other docker it will put the files in /mnt/user/Media/... because they are the same location(?)

Correct.

 

I think the that the idea of paths inside the containers not being the same as the paths outside the container is what new users find hardest to get their heads around.  Once that is clearly understood then dockers become much easier to use.   

 

Hopefully at some point some rally good tutorials will be put together on this subject that we can point users to (especially as much of any such tutorial would be generic docker and not unRAID specific).

 

 

This is how i have it set up

This is totally wrong, but without seeing your docker folder mapping, it's impossible to tell you how to fix it. Post a screenshot of the docker setup for this container.

it should be in that imgur album

You are right, it was, but the black background hid it from me. You need to set the "Download to:" field to /data, because that's what you have set as the mapped folder. Any subfolders that you set up in the other fields need to have /data as the root of the path.

okay, I'm somewhat following i think. So is the only thing that i need to change is the "download to" field?

 

Should i change it so that it downloads it to my user/media/... in case i add more disks? I just have it going to disk1/Media/... because i was trying to figure out what was going on

The key point to realise is that the first screenshot shows the paths as seen INSIDE the container and are not visible at the host level.  These will be equivalent to the values in the Container Volume field when setting up mapping.  You want to make sure that each path is mapped to a Host Path that is somewhere on your unRAID system.  Any container path that is not mapped properly to a host path will result in files being written inside the container - something you definitely do not want as it would fill up the docker.img file holding the container binaries.  Note that you can change these mapping entries at any time by Editing the Container properties (while it is stopped) so it is not critical that you get them perfectly right initially as long as they are all mapped to locations outside the docker container.

okay, I think I understand now (I hope).

 

So technically /data = /mnt/user/Media/... Correct? So if I point to /data inside of Deluge or whatever other docker it will put the files in /mnt/user/Media/... because they are the same location(?)

Correct.

 

I think the that the idea of paths inside the containers not being the same as the paths outside the container is what new users find hardest to get their heads around.  Once that is clearly understood then dockers become much easier to use.   

 

Hopefully at some point some rally good tutorials will be put together on this subject that we can point users to (especially as much of any such tutorial would be generic docker and not unRAID specific).

thanks! That makes it a bit easier. I was trying to find stuff on the internet but I was coming up with nothing. I don't know do it just wasn't there or if it was my search terms that were wrong.