I use dozzle to monitor docker logs and it is great. It also has good stats for each container.
It will not alert you on thresholds if that’s what you mean
I can try it. I would be nice to alert. Maybe if it is output to openmediavault notifications I can use it (with the help of a script in sink.d)
Hi to all,
Any suggestions to monitor the docker containers in regards memory/cpu? I have some containers with constrains and I would like to see when the pass a specific threshold.
Are in host mode or bridge? I guess with tcpdump you may get some information but I don't know that you need to look to designate that this traffic is coming from the containers. Never really thought about it.
Actually I was reading the openmediavault-compose documentation, not the docker on OMV. Easy to miss this information. Perhaps a bit spread information between pages.
I just faced the same with a path in mergefs and exactly the same message as in RE: Installing docker creates an error
The metadata.db was there so no chance that was wrong the path and I also used the srv/mergefs/<pool_name>/docker. Switching to ZFS path, worked without problems.
It seems that docker(?) doesn't like to be on the such kind of volumes made by mergefs or unionfs.
Perhaps it is good to be on the documentation as warning.
Hi guys,
Another question about something that it is not yet on the documentation (no judge, questions like these will help others till the update)
In the backup->actions there is maintenance and container state. What exactly are doing these two options?
Hi,
Because the documentation doesn't have it yet, I want to ask what exactly is doing the "configs" tab in the compose plugin.
I'm wondering what kind of problems you may have with the MB/CPU combination which is not latest gen (not even 3 before), with ZFS (and kernel headers of Proxmox).
Linux kernels usually they have issues with newest generation rather old (fyi, base kernel supports still i486 and Pentium for now)
I had also Broadwell gen CPU (older) with ASRock Rack MB and I didn't had any issue in regards ZFS, kernel headers etc.
ok! thanks for the answer
Hi,
I stuck and I can't find the information. I have set a property in zfs dataset to x value and now I want to remove this value, effectively remove the local source and take whatever value is inherited. How can I do this from the GUI? (CLI I know, just avoid some not synced settings)
I see. I'm just try to see (again for the average home user containers) where (and maybe which of) the extra features can used. Also I see that there is a bit more complexity comparing docker/podman which I can't see if worth.
Hi to all,
This could be look either strange or provocateur or either stupid question but I want to ask what can be the use case of K3S for a home use. I know that it is an advanced feature.
I believe that most of us (advanced users or not) we have some containers like pi-hole, plex, sonarr or radarr maybe some mariadb. What can be the benefit/value (other that playing and learning kubernetes) to have such kind of containers in k3s?
yes, I see it. It is just makes things little organized.
I like the idea, I already have vcs (forgejo) in my openmediavault so I can use this option. Just need to use the correct directory 
no worries for the documentation. This local git repo is been created where all the compose files are stored (as defined in the options), right?
Hi to all,
I would like to ask what is the propose of this option which recently introduced in Compose plugin in Files/Tools section. I don't see in the documentation any reference.
Hi,
Today I had a network issue as I describe in another thread which somehow I solve it. I don't remember to be fair how was the setup before that but breaking the bond and re-create it, I left the interface in DHCP. As I saw in another thread (RE: OMV address is 127.0.0.1 ... ?) and correct me if I'm wrong, the new IP will be added in the /etc/hosts. In my case is not and unfortunately cause issues with Nginx Proxy Manager where I host in the same machine together with some containers (tries to redirect to 127.0.0.1).
Is it the case that with DHCP the IP will added on /etc/hosts or understood wrongly (or I fell on some bug)?
btw: I had exactly the same issue today with the same kernel (Intel NICs). Even if I break the bonding didn't work till (coincidence?) a live cd. What I notice is that the interface names changed (not to predicted).
