I unterstand your point of view....would it be possible to add a switch or something to delete all files from docker, if the user wants to?

Docker GUI plugin now stable
-
- OMV 2.x
- nicjo814
-
-
Of course you already have the delete image and delete container buttons. Both do multiple selection. So you basically have to press two times the delete button. The install/uninstall plugin framework doesn't provide interaction so it's not possible. From terminal it might be possible, postrm routine.
-
I´ve deleted the containers and images before uninstalling the docker plugin....but the files in /var/liv/docker stayed untouched. So they eating up a lot of space on the system drive....
-
-
Images and containers use most of the space. Maybe you have unmapped data volumes there, those cannot be managed from the plugin.
You don't need to use the os drive btw, the plugin can pass the argument to the daemon to change the default docker folder (use a shared folder) or you can use a symlink to a data drive(my preferred choice). -
Oh that could be the solution....i´ve mapped all my Media Drives in the emby container....
Thanks, i know that i could change the default folder....but i want it on the system drive so it gets backed up when i run a clonezilla session
-
Just going to jump in here and echo what subzero said - it's likely all the leftover container/image data that doesn't get removed with the plugin. Just the same as if you removed docker yourself manually, it will leave all that stuff.
My suggestion, would be to just first re-enable the plugin. Then once it's enabled (aka docker commands are available) - pull up the command line and run <tt>docker system prune</tt>. This will remove all unused images, volumes, containers, etc. It's a one line command that everyone in the docker world has been waiting for rather than doing old commands searching for lingering containers and contents, piping that into another command to remove, etc. Once done running that - it will also output a "X amount of space reclaimed" information tidbit to indicate how much was cleaned up. Then you should be able to remove the docker plugin and you'll be in good shape. If there is ANYTHING leftover, it's should be small in size and likely just some temp/system files.
-
-
Very good hint...thanks for that.
-
The testing package is updated now with the the start, stop and restart button merged, also the incorrect variable parsing is fixed now.
-
I tried to download and install, but seems it's not showing up in Updates after I upload it. Possible the version needs to be incremented so it appears as update?
-
-
Need to install with dpkg in terminal
-
Ohh, did something change? Last couple times you've made updates with it, I simply uploaded it through the plugins section, checked the updates which showed up, then installed the update. Worked like a charm. No biggie, just curious what would have changed.
-
Maybe try clear the cache since is a gui change
-
-
@subzero79 I've just installed a new omv3 dev system that I will try your changes on. From what I'm reading you've done some superb work! I'll keep an eye on github to see when your changes are merged.
-
I forgot. I'll do the pr tomorrow. Thanks
@subzero79 I've just installed a new omv3 dev system that I will try your changes on. From what I'm reading you've done some superb work! I'll keep an eye on github to see when your changes are merged.
-
I've started working on a new tab that will let the user list networks and also create/delete macvlan networks (to begin with). The listing is done and create/delete should be possible to complete quite soon.
-
-
@anderbytes Which parameters would you recommend to be able to set when creating a macvlan network? Right now I have name, subnet, gateway and parent. Anything you feel missing?
-
@nicjo814 there is an issue when using the plugin with zfs systems and the shared folder selector. Iirc this is a bind, since the bind is in fstab the fstab-generator of systemd doesn't know how to create/relate a dependency there since zfs mounts are not fstab related. I haven't been able to confirm this in a testing vm, but there is a thread around. in the future it might be better to remove that option leaving a note to use just a symlink imo.
-
I think you are right @subzero79. I think I saw something about issues with using symlinks, thus I went with the bind option. But that was ages ago and my memory is most probably wrong
I'm using ZFS myself so I'd probably run into this issue when upgrading (soon...) to OMV 3
EDIT: BTW, creation and deletion of networks is done. Just need to test it properly...
-
-
@subzero79 I noticed that the changelog looked "strange". Did you use omv-dch to increment it or the "standard" dch program? The omv-dch script wraps the dch program and adds some standard text to the changelog.
The wrapper can be found here: https://github.com/OpenMediaVa…b/master/usr/sbin/omv-dch -
I can't make macvlan work on my VirtualBox dev environment (in Ubuntu). Anyone have this working?
EDIT: The network interface gets created ok withing the container. However I can't access the outside.
I'm using the PCnet Fast III adapter in promiscuous mode and have tested both bridged and NAT mode... Running out of ideas
Participate now!
Don’t have an account yet? Register yourself now and be a part of our community!