MergerFS pool disappears for no reason

Zitat von Copaxy

Interesting, so if i understand it correctly, if i use the omv compose plugin it saves the data in the docker root folder? Or am i able to save the config data somewhere else like when i use compose in portainer and i set the config and container files to be in whatever directory i choose.

For example i create a docker compose for jellyfin and i put the path for the config at my prefered place but the rest of the container files are in the docker root folder.

What is the difference when i use the compose plugin?

The first part, yes that's correct.

The 2nd part...

The docker-compose plugin.. it basically lets you run docker-compose from the OMV webUI.. but in additiona to that, it saves your compose files in a specified folder.

We need some docker lessons here about what data is stored where and what data is important.

Zitat von Copaxy

if i use the omv compose plugin it saves the data in the docker root folder?

NO. It stores docker images, docker containers, and docker volumes in the docker root folder. Images and containers files are easily replaceable and not important. docker volumes make path management easy but use the root folder (not ideal). If you specify a full path for your volumes, the data, which is the ONLY important thing, is stored exactly where you tell it to.

The plugin also stores the compose files in the database and a sharedfolder. With portainer, if your portainer container is not working right, it is very difficult to access your compose/stack files.

Zitat von Copaxy

Ah so it is like docker-compose on portainer but with a additional save in another folder

NO. The compose plugin does NOT use portainer at all. It literally runs the docker-compose binary from the host OS against compose files on the host OS. It is not running in an additional container like portainer. It is much simpler. When you use it, you pick where the docker root folder is by the path in omv-extras. You pick where the compose files are by choosing a shared folder. You choose where the important volume data is by specifying a full path for each volume in your compose file.

Zitat von d13m

How to create macvlan network via plugin

The compose plugin? It doesn't create any network. Your compose file should. First example I found - https://github.com/sarunas-zil…master/docker-compose.yml

Zitat von d13m

start/stop/recreate container?

There is an up button in the Files tab to start all containers in the compose and a down button to stop all containers. If you starting/stopping/recreating individual containers in a multi container compose file, you are doing it wrong. If you just want to update the images, there is a pull button to pull the newest images and then the up button will restart the containers in the compose file that have a newer image.

Zitat von d13m

but Portainer is more familiar to me

If you use stacks in portainer, then the compose plugin is about the same.

Zitat von d13m

plugin without documentation, didn`t find manual or guide.

Yep, docs haven't been written yet. If you have ever used docker-compose, it is pretty much self explanatory though.

Zitat von Copaxy

Does someone know where the mergerfs plugin in OMV stores its configuration data?

in the mergerfs section of the omv database.

Zitat von Copaxy

Any ideas on how I can check, if mergerfs still has some old settings stored somewhere and I then how can remove them?

sudo omv-showkey mergerfs But if there was "leftover" settings, then the pool would show up in the plugin. The plugin shows everything in the database not just things mounted.

I would highly recommend to stop uninstalling the plugin to "fix" things. I don't ever test this and don't want to.

Zitat von Copaxy

Is there any other way to check how mergerfs still sometimes creates the old pool?

you could have a leftover entry in the mntent section of the database or less likely, a leftover mount file in /etc/systemd/system/. If you are only uninstalling the plugin for fresh installs, neither of these should be a problem.

Zitat von Copaxy

Is there a possibility an old parity drive could mix up OMV?

No. A parity drive from snapraid is just a normal filesystem with a parity file on it.

Zitat von Copaxy

If it occurs

What is it? An extra pool? The pool doesn't mount?

Zitat von Copaxy

that the old PoolA still sometimes shows up after boot and then PoolB is not mounting of course.

How do you know poola "shows" up?