prime95 in a Docker container issue/question
 

*****
It was suggested I post this question/issue in the Software form so I'm copy/pasting my original query here. The old thread can be found here: [url]http://www.mersenneforum.org/showthread.php?p=473044#post473044[/url]
*****

I'm experimenting on different way to run/deploy prime95 and I thought maybe having the program in a LXC or Docker container would be an easy way to deploy to many machines.

However, I have an issue. It appears that a Docker containers are non-persistent. (Meaning that any changes written to disk within the container are lost at the next power down of that container.) Yes, you can "mount" another folder outside of the container but that kind of defeats the purpose I'm trying to get at... UNLESS, there is a way to run mprime within the container, along with some of the permanent files (like prime.txt) but then store the non-permanent files (like local.txt and worktodo.txt) in a mounted directory outside of the container (thus they would persist after a power down of the container).

Sorry, a bit long winded. In short, is there a way to put local.txt, worktodo.txt (and other changing files) in a different directory than where mprime runs?

*****
Thanks to Dubslow and S485122 for helping with "my" way of possibly solving this issue.

That said, has the mersenne/prime95/GIMPS organization thought of building a LXC/Container for ease of deployment? One of the most beautiful things about doing it this way is that you'll only need to support 1 or 2 versions of the code instead of building executables for each OS platform (Linux, Windows, MAC).

Thoughts?

Have you tried using symbolic links? No idea if that will work though, since I haven't had the need personally.