ZitatMight be browser cache.
ZitatTrue. Try to temporarily disabling cache by setting the
appropriate checkbox in the chrome debug console (can be a bit tricky to
find, but there are settings for the debug console itself). Then reload
the GUI with the console open to bypass cache.
True. No error in Chrome, only in FF. Issue solved. Thx.
Here is some feedback. Once a container is created, there doesn't appear to be a way to change the settings. For example I want to change the host port to use a different port. The only way I could do that is by deleting the container and creating a new one, or by cli. I also think it would be nice if you could go back to the settings for a container. Maybe double click on the container name and the settings window appears or add a button to do that. Just my two cents. Other than that it's working well for me. 
Actually I didn't think Docker allowed you to change the settings of a created container. Need to look into that.
I think you are right. I was just wondering if it was possible. Sorry for any confusion.
Ok, no problem That was actually the reason for implementing the copy function. It's not exactly what you want, but I think it's as good as it gets right now when Docker doesn't support change of settings...
You can't change settings, what you can do is save changes inside to the image like docker commit <container> <image>
Hello,
I don't had time for testing the last days.
But today I updated to the new version, with some downloaded images and running containers in the original base path.
Then I changed the base path, but the downloaded images didn't move/copy to the new path.
After i copied everything from the old base path to the new subfolder everything was O.K..
Maybe you can implement the moving of existing files to the new folder, like for example in the mysql Plugin.
With the new version I also don't have the problem with the grub parameter. I don't need to put them in /etc/default/grub.
NICE WORK 
but the downloaded images didn't move/copy to the new path.
There is a button to copy all the containers.
Hello,
I tried to mount an volume into a container.
To do this I put during "run image" under "Volumes and Bind Mount"
host path: /media/a61ffa91-fcac-4fb1-9ee2-c06f9083bde9/s_fhem
container path: /opt/fhem
But the Folder doesn't appear
The Details from this container are listet in the attached file "from_WebIF.txt"
When I run from the console
docker run -d --name=server-fhem -p 8083-8085:8083-8085 -p 7072:7072 -v /media/a61ffa91-fcac-4fb1-9ee2-c06f9083bde9/s_fhem:/opt/fhem dockerbear/dfhem
the folder appears in the container
Details from this Container are listet in the attached file "from_Console.txt"
Is the "Volumes and Bind Mount" function not the same like the "-v" option, or did I something else wrong?
Thank You,
that was my fault 
It's a bit undocumented
So it fits well into the project.
Greetings
David
Is there a How-to to get started?
edit: I never used docker before so I'm sure I'm missing something obvious I installed the docker-gui 02.12 and pulled an image to test it out (hurricane/tinymediamanager), but not really sure what's the next step is to start it. I created the docker container with that image, but the start button is grayed out. in the MyIP:9200 it shows up in images but not in containers.
I am writing a guide, but is not finished. Press the info button it will take you to the webpage to set up everything.
To run the image well press.......Run Image and
Select ports in the container and in the host, press the ADD button otherwise it won't add the parameters. The port 3389 is for remote desktop in this case i guess, so you should be fine by adding the 8080 only, the webUI. If you don't want to add ports change network mode to host instead of bridge
Same you do for the path mappings. A quick look at the webpage indicates a path is for keeping the settings, the other is for the path or location to the media. Again don't forget to press add otherwise the parameters won't save.
The press save and the container will be running, go to the app webui in their respective port
This is how it should look, aprox
Thank you very much for taking the time to help! Wow - Now I see how powerful Docker together with OMV is. Not sure if this is the behaviour with all docker images, but with tinymediamanager I can now run a session from my Samsung phone, walk over to my desktop and it automatically picks up where I left it.
(Now I just have to figure out why it doesn't allow to save files or rename folders)
Usually this containers run the process inside as "un-rooted" user, in this case is usually user name nobody (99). In this particular image this user nobody inside the container belongs to group users (100), so the container should not have problems writing to a default share of omv
You can reset the permissions to default with the tab next to shared folders. If that doesn't work try opening the folder to 777 mode
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!
