Hi,
I wanted to know if i remove the docker plugin, will i loose all my containers and volumes and settings? I want to manage docker via portainer instead of the docker plugin but if i can keep my configurations, it will save time.
thanks
Hi,
I wanted to know if i remove the docker plugin, will i loose all my containers and volumes and settings? I want to manage docker via portainer instead of the docker plugin but if i can keep my configurations, it will save time.
thanks
It shouldn't remove the docker engine, so all containers/images should remain. In cli you can try
apt-get purge openmediavault-docker-gui
Then it will tell you what packages will remove, besides the plugin.
ok, i will try that.
It shouldn't remove the docker engine, so all containers/images should remain. In cli you can try
apt-get purge openmediavault-docker-gui
Then it will tell you what packages will remove, besides the plugin.
root@SRV-Saitoh-app:~# apt-get purge openmediavault-docker-gui
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
docker-engine git git-man imagemagick-common liberror-perl liblqr-1-0 libmagickcore-6.q16-2 libmagickwand-6.q16-2
php5-curl php5-imagick
Use 'apt-get autoremove' to remove them.
The following packages will be REMOVED:
openmediavault-docker-gui*
0 upgraded, 0 newly installed, 1 to remove and 1 not upgraded.
After this operation, 392 kB disk space will be freed.
Do you want to continue? [Y/n]
Alles anzeigen
Does this mean docker-engine will still be installed and work? Or will i have to reinstall docker engine? Also i setup my docker data path in the plugin, i guessi i can still leave it there and set the docker data path in a env variable of some kind.
It says there is no longer required by the plugin. docker-engine will remain.
One more question about this..
i am having a very anoying issue. I am using the docker plugin in openmediavault. When i reboot all the config folder i mapped to variables get there permission changed to 911. I set the PID and GID using the env variables to my user when i start the container. I figure the 911 is the docker user? Is this normal behavior or the plugin doing this?
all the containers start and the apps run but i have rw issues cuz the config files on the host have all there permissions changed
911 is common uid for linuxserver images. There must be a script running at the start of the container changing permissions. Nothing new there, common practice. You can set the puid to another number.
911 is common uid for linuxserver images. There must be a script running at the start of the container changing permissions. Nothing new there, common practice. You can set the puid to another number.
but i set it
Where's the source for that image ?
Where's the source for that image ?
i traced it back to lsiobase/mono and then to lsiobase/xenial (this one contains the adduser command that seems to mess up everything).
I was thinking of creating a user and group with the 911 uid/gid
That's sonarr, i use the same image. The start script changes ownership only on /opt/Nzbdrone, not /config
according to
https://github.com/linuxserver/docker-sonarr
It's working here, maybe change ownership of /config to 1000:100 and restart it, see if it changes again
The permission changing is happenning to my files on the host that are mapped to the /config volume. It doesnt happen when i restart the container, only when i restart the docker plugin
only when i restart the docker plugin
There is no plugin restart
If you mean restart the docker engine, that's basically the same as restarting the container. I absolutely have no idea what would cause that.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!