Volume mapping in portainer
-
- OMV 5.x
- TechnoDadLife
-
-
What am I missing or forgetting to map it to my downloads and media.
You select Bind not volume, at least that's what I do.
-
Opps, You are right.
Thanks!!!!
-
Second question.
So we don't actually have to map a drive in the OMV GUI when we set up Portainer, because we can map it in the Portainer Docker?
-
So we don't actually have to map a drive in the OMV GUI when we set up Portainer,
are you referencing when Portainer first installs? as Portainer creates a volume -> data_portianer or do you mean where the containers are installed?
What I did in OMV-Extras was to change where the docker containers would be stored, this was on a share I created simply called docker-> Save, then installed Portainer
This is unlike OMV4 as in your video you create a folder Portainer under AppData and pointed the /config to that, in 5 the /config is under data_portainer volume.
-
The plugin in probably running the commands which are given by the original documentation:
Code$ docker volume create portainer_data $ docker run -d -p 9000:9000 -p 8000:8000 --name portainer --restart always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer
This way the volume portainer_data is created in the docker root dir.
You can find find it with docker volume inspect portainer_data -
The plugin in probably running the commands which are given by the original documentation:
Correct - https://github.com/OpenMediaVa…in/omv-installdocker#L247
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!