Nem
-
Posts
177 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Nem
-
-
makes perfect sense, thanks
In that case, is there a plugin that will create a backup of the cache drive so I don't risk losing my appdata/config data in the event of a cache drive failure? I've seen some scripts floating around the forum, but something like a plugin would be useful
-
if, for all of my containers, I point config to some data disk, then the only thing stored on cache would be the docker images right? In other words, config = appdata? No appdata is created by docker unless you explicitly point something to it during container config?
-
That is really up to you. The configuration information for dockers is held on the flash drive, so it is normally easy to re-instate dockers and their configuration if the cache drive fails (or is corrupted for any reason). Many applications are simply downloading data and then writing the results to a user share so that it ends up on the data drives for longer term storage.
Most containers ask for a config path. I assume this is config information for the application within the docker container. Should this path point to the cache on the host? Or one of the data drives? Or the flash?
It's easy enough to reinstall a a docker container if the cache drive dies, but some applications might have more complex settings. For example, with deluge theres the entire preferences pane you need to set up for the application itself. I assume those settings are stored wherever you point your config file to during docker container installation.
I guess my specific questions are about where different types of docker information are stored:
You mentioned config info is held on the flash drive. Is this just template information for how to do the initial docker container setup (i.e. when you add a container on unraid)?
I believe the container image is stored in the docker image file when docker was first started. I assume this doesn't contain any actual config info?
The the config for each application (e.g. deluge) are stored wherever you point /config to during setup. I assume this is pretty small and would not actually benefit from a faster drive (i.e. cache) and can/should be stored on a data drive if you want to retain the application config info if the cache drive dies?
-
how do you enable a site, or create a default site with this?
-
oh so is /mnt/disk1/Media actually a disk share, even though I've explicitly turned off disk shares in the settings? I thought it just referred to a directory on the drive?
If I should use user shares, then the situation gets more complicated, because the Media folder shows up for every user /mnt/user/Media, /mnt/user0/Media, giving me even more options...
-
I have set up every user share on my server to use one, and only one, disk. For example, I have a user share Media that is on disk1 and nowhere else.
When setting up docker containers, often you're asked to map to a place on the host. If I wanted to pass Media through to the container, it appears I have 2 options: /mnt/disk1/Media or, because the share is accessible by users, I can use /mnt/user/Media
In other words, the Media directory shows up in multiple places. Which is the correct host location that I should be using when doing the mapping? Does it make a difference either way?
-
I have plex media server set up and everything is working nicely. However, when I visit the webgui, it forces me to log in to my plex account. This is fine because I have a plex account and all is good, but other people that use the server at home do not have a plex account (and my account does not allow for sharing).
Is there a way to disable the log in so that 1) I can log in and access my content using my account, and 2) does not force a login for those that want to watch media without an account?
-
ah that did it, just needed a restart and it worked, thanks!
-
access is no problem. I changed the name from unraid to server, and can access all shares with either \\server\media or \\192.168.1.10\media
If I map a network drive, everythings works too
My issue is not being able to see the server in network locations. If you open up windows/file explorer, in the left hand pane there is a section called Network. When I click on it I can see all the machines on my network, but unraid (or linux machines in general) do not show up here. There are some shares that I don't want to map as theyre not used that often, and I don't want to type in the address manually whenever I want to access it, so being able to see it in network locations is important
-
I couldnt find anything on the forum regarding motherboard sound
If I were to purchase a gpu with a hdmi output, and I pass that through to the VM, will I automatically get sound via hdmi on the graphics card, without having to explicitly pass through a separate sound card?
-
yeah that didnt fix the issue for me. Maybe our problems are slightly different as I don't see how a host file edit would cause the server to show up in network locations
-
webgui seems to work but I can't seem to access delugevpn using the GTK client on windows
During delugevpn setup, I made sure to set lan_range to 192.168.1.223 (ip of my desktop machine) so I can access the server. I edited the deluge/auth file and added user:pass:10 on a new line
Tried to connect to the server, on port 58846, using the user and pass I setup in deluge/auth, however the circle is red and won't let me connect
Am I missing a step somewhere?
-
I'm planning on running steamOS in a VM, but I don't have a pcie graphics or sound card, both are on either the cpu or the motherboard
I tried setting up a VM to pass both through but no options show up when setting it up
Does passthrough not allow for onboard video/sound?
My motherboard: asus h87i-plus
cpu: intel pentium g3220
Eventually I'm planning on purchasing an nvidia pcie graphics card, which I should be able to pass through, but planning on still using onboard sound. If sound doesn't work at this stage, I guess it wouldn't work in the future either?
-
A user share results in a subdirectory with the name of the user share being created on each disk in the user share containing data. So if you have a user share called FISH configured on disk1 and disk2, each would have a folder called FISH. Now the tricky part is what happens if another disk, say disk4, also has a folder called FISH. Unless that disk is globally configured to not participate in any user shares, disk4 will become a somewhat reluctant member of the FISH user share. All its FISH files well show up with the user share. If a file on disk4 is updated via the user share, the update will be written back to disk4. New files well still tend to be written to disk1 or disk2, but even this is not assured. It depends on the split level and the existing subfolders present on disk4.
But surely this wouldn't happen if 1) no top level directories on any of the disks have the same name and 2) each share is explicitly told to use only a single disk?
This condition most often happens when a user attempts to remove a disk from a user share. Changing the configuration to remove a disk does nothing with the folder on the removed disk or its files. Once they figure it out, they might try to copy the files form the disk share of the disk they are trying to remove to the user share. This is a deadly mistake. Called the "user share copy bug", copying from the disk share to the user share will result in unRaid trying to copy files over top of themselves. Normally an OS would detect this and give an error, but in this situation the OS is oblivious. And the attempt will result in each and every file in disk4's FISH folder getting truncated to 0 bytes, losing all their contents.
Right now, I have 'enable disk shares' set to No, so even if I remove a disk, it shouldn't turn into a disk share anyway right? In other words, the files would not be visible for me to copy them to another location
Please correct me if I'm wrong because that sounds like a big bug, but with my intended setup I don't believe I'd ever run into this situation? For example:
Disk 1 contains a folder 'Media', then set as a user share (told explicitly to use only disk 1)
Disk 2 contains the folders 'Games', 'Backups', then set as different user shares (both told explicitly to use only disk 2)
So none of my top level directories share the same name. And if I were to remove a disk from a user share, well, my user shares are told to only use 1 disk, meaning the entire user share should be gone anyway.
Can you think of a way with this setup where I'd run into this bug?
-
ah I see. Looking at the problem a different way then - is it possible to check on windows machines whether they are the local master, and force them not to be?
-
Looking for some advice on a recommended way to set up my server, particularly as it pertains to docker setup.
I have:
- a 64gb SSD as cache
- 3TB parity
- 3TB data drive for my media
- 3TB data drive for backups and other random things
I'm planning on running the following:
- plex
- mariadb
- couch potato
- sonarr
- deluge + openvpn
- kodi/xbmc
- steam os
So, with docker, I understand there is a docker image file that needs to go somewhere, and an appdata directory? I have a few questions:
1. I read in the docks that its typical to put the docker image on the cache drive, but what about appdata? In my mind, cache = temporary, so it feels a bit strange to put appdata on the cache maybe?
2. Am I correct in thinking that appdata should not be a share, but rather should be some root level directory, wherever you decide to put it?
3. Any downsides to putting appdata on slower (5400rpm WD red) data drives? What about the docker image on a slower drive?
4. Is it more typical to just have a single appdata for all applications? Or to have different ones, one for each application you intend to use?
5. I'm assuming that if you have the above applications running 24/7, the docker image/appdata will be in constant use. Therefore, if I put those files on my "random stuff" data drive, will it just keep that drive constantly in use? maybe causing some slowdown for either the applications or transferring files to/from the shares on that drive?
6. Does putting docker/appdata on the cache drive basically then require the use of a cache pool in case the cache SSD goes down and taking all the applications with it?
I'm trying to be conservative with my use of the cache drive due to it only being 64gb, but I don't want to slow down the server by dumping everything on the slower WD red drives either.
How would you suggest I go about organizing the docker related files?
-
Ill keep an eye on that thread. I seem to remember I had the same problem when I set it up originally as a debian server, and then a ubuntu server. Nothing seems to play nice with windows
-
how does one set a router as local master? I couldnt find the option for my AC68u
I thought unraid sets itself as the local master by default? That's the way its set during my first install anyway and I appear to have a similar problem as OP
-
I have set up a user share on unraid, with the correct user privileges, but I cannot see the server in windows 10. When I go to file explorer > Network, the server does not show up there. However, if I directly use the ip/hostname (\\192.168.1.10) I can access the shares OK
How does one set a share to be browseable in windows?
-
sounds easy, thanks! testing out the trial version now...
-
My understanding of disk shares is that the contents of an entire disk gets shared out to the network, while a user share is a specific directory that gets shared (but can be spread out amongst multiple disks)
I want to set up user shares (as I don't want entire disks to be shared), but is it possible to force a user share to store data on only one specific disk? I ask because I want to keep all of my media on one hard drive, backups on another, so that if I needed to pull a drive from the machine I know exactly whats on there and that it contains everything I need.
I dont want to set up a disk share because sometimes there will be directories on a disk that are not meant to be shared for one reason or another.
How does one set this up?
-
Dockers are not full vms, look at it like installing an application, they do not mix with each other snd cannot see each others data, it is possible to have them both look at the same data though, you have to configure it.
By look at the same data I assume you mean if you have a share set up, you can configure dockers to see those shares? What happens in the case of mariaDB, where other dockers need to be able to see the data (database) within the mariaDB docker?
-
I can answer question 2 for you. There is a Deluge container with inbuilt VPN client (DelugeVPN) that you can use. There is no need to SSH into the container, all VPN settings are done in a config folder outside the container. It’s only the traffic for the Deluge container that goes through the VPN.
I currently have the setup on a raspberry pi, but I also have scripts that auto restart deluge/openvpn if they ever go down. How does one set things like crons and execute scripts within docker containers to achieve this? Because I imagine the config folder for docker containers only contain configs directly related to deluge/openvpn in this case, and not crons/scripts
-
I am tempted by the possibility of switching over to unraid, but I'm having some difficulty in understanding Docker. I have 2 situations that I'm unclear about:
1. I want to run mariaDB in one container, Kodi in another, and nginx in yet another. I want nginx and kodi to both be able to access mariaDB - how easy would this be to set up? My understanding is that docker containers are isolated from one another, so is it relatively simple to get one container to talk to another? I guess an extension of this question would be, do docker containers get their own internal IP? If so, I imagine I can just point the nginx/kodi config files to the IP of the mariaDB container?
2. I want to run deluge in a container. I also want to be able to install an openvpn client within the same container. Do these containers exist as virtual machines? How easy would it be to SSH into the deluge container, do all the legwork of installing openvpn, related scripts etc. manually? I can understand the process if these are just linux VMs, but I'm not sure if docker containers would change this process at all. Also, would the traffic from the entire machine go through the vpn? Or only deluge traffic from within the same container? I'm looking for the latter
[ARCHIVE] binhex docker repository
in Docker Containers
Posted
regarding delugevpn:
1. Is there a killswitch built in such that internet connection gets cut off if VPN loses its connection?
2. Is there an autorestart for deluge and openvpn in case the daemon crashes?