bradlewa

No, I haven't tried that. So it's a bit more complicated than I implied above. I actually had moved an original bare metal install of windows to a vm, and have an ntfs partition that was originally on that system that I use for my steam library. So for the 2 other vm's that I mentioned above (true actual vm's), I was mounting that ntfs partition as a separate mapped drive - but can only boot up 1 of those 2 vm's at the same time. Is it possible to mount an ntfs partition as an smb share for the vm's?

So my system has 2 discrete graphics cards and 2 windows VM's setup with a graphics card dedicated to each of them. A 'standard' 2 gamers on 1 PC setup. Each vm is installed on its own vdisk of course, but in order to save ssd disk space I had created a single partition to share game installs between the 2 vm's. So in Steam, I use the 'shared' partition as the library install point, and when either vm is loaded they can access the installed game. Only recently did I actually try to run both vm's at the same time and discovered that when one vm is running, it locks the 'shared' gaming partition and prevents the other vm from running. In retrospect this makes sense since I'd imagine it would corrupt files if 2 systems were writing to it at the same time. But is there any way around this? Is it possible for the 2 vm's to be 'aware' of each other, still mount the shared partition, and just prevent files in use from being loaded (i.e. the same game or save game file)?

I've installed this docker, which is pretty awesome by the way, but I have a question about keeping changes persistent. From my understanding, and experience, let's say you use apt-get within the ubuntu vm to install a new application. Then you decide to make a change to the docker configuration in unraid (say adding a new port that gets carried through), which results in the base image being reloaded and you lose the changes you made (i.e. the newly installed application). Is there any way around this? One thing that I saw you can do is to map /etc from the ubuntu vm to a directory on the cache drive in unraid. Do you see a downside to this? EDIT: Actually just saw that I can't even start the docker when I do this, so clearly it's not a viable option. Back to the first question - any way to keep something persistently installed? Say apache for example...which installs to /etc/apache2.

I'm new to Docker, so these questions might sound dumb. I'm running unraid 6 beta10. In the Docker tab of the GUI I have 2 entries for Crashplan. I must have set one up via the GUI using the template from gfjardim. Then after that, I used the command line, since I thought that was necessary to start the app. After looking at the entries, it looks like the first one didn't actually do anything (no ports are listed), so I'm assuming the first entry is unnecessary and can be deleted? The second thing is with respect to uncommenting the machine address and port number in the ui.properties file in the Crashplan app on my computer I use to access the unraid server. If I remember correctly, previously when using Influencer's Crashplan plugin, you would recomment those lines once you were done setting up the backup. Do I need to do that here as well? Or is it ok to leave it uncommented? Thanks for the help! One additional followup I thought of after I posted. When I used the command line to setup the Crashplan Docker, I set the path to my config as a new folder called /mnt/user/appdata/crashplan, likely because I saw that example somewhere. This folder didn't actually exist before, so the command created one. But now this shows up as a new share, and it is not on the cache drive. Should it be? And if it is supposed to be on the cache drive, can I change the location of the config folder after the fact to my normal app folder on the cache drive (in other words, can I change the setting in the docker entry)?