omv-extras 6.3 / openmediavault-compose 6.7

    • Official Post

    Thanks to chris_kmn for updating the nvidia transcoding guide with notes about the compose plugin. Please read the guide again if transcoding is not working - RE: [HowTo] Nvidia hardware transcoding on OMV 5 in a Plex docker container Installing the plugin fresh should automatically leave the docker storage path blank if you have existing nvidia transcoding daemon.json changes.

    omv 6.9.0-1 Shaitan | 64 bit | 6.2 proxmox kernel

    plugins :: omvextrasorg 6.3.1 | kvm 6.2.16 | compose 6.10.3 | cputemp 6.1.3 | mergerfs 6.3.7


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    Like 1
    • Official Post
    Quote from ryecoaaron
    Code
    openmediavault-compose (6.7.16) stable; urgency=low

  * Add Volumes tab to display information on docker volumes
  * Add Networks tab to display information on docker networks
  * Set Docker storage path to blank if nvidia is detected in docker
    daemon.json to prevent custom config from being lost

    I really like those changes. :thumbup: :thumbup:

    If you added a button in the network tab with docker network create it would be very helpful, it's one of the few things I miss about Portainer I think. Just a suggestion...

    Quote from chente

    I really like those changes. :thumbup: :thumbup:

    If you added a button in the network tab with docker network create it would be very helpful, it's one of the few things I miss about Portainer I think. Just a suggestion...

    I like the Network tab, like you, I wouldn't mind a Network create, but again it's not a biggie as that's quite a bit extra to program in.

    • Official Post
    Quote from chente

    If you added a button in the network tab with docker network create it would be very helpful, it's one of the few things I miss about Portainer I think. Just a suggestion...

    I know... I still don't understand the need but I am working on adding it. I decided I wanted the compose plugin to resemble the kvm plugin a bit more and the kvm plugin has the volume and network tabs.

    omv 6.9.0-1 Shaitan | 64 bit | 6.2 proxmox kernel

    plugins :: omvextrasorg 6.3.1 | kvm 6.2.16 | compose 6.10.3 | cputemp 6.1.3 | mergerfs 6.3.7


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    Thanks 1
    • Official Post
    Quote from ryecoaaron

    I still don't understand the need

    I'm used to joining certain containers on the same network in this way. I know it can be done from the same yaml file, but I find it more... easy? comfortable? It's just how I learned to do it and have continued to do it that way from CLI since I left Portainer months ago.

    Quote from trythat

    I like the Network tab, like you, I wouldn't mind a Network create, but again it's not a biggie as that's quite a bit extra to program in.

    You're right, it's not a big deal. Like I said it's just a suggestion and in reality networks are not created very often.

    Although this could be like opening Pandora's box. If you make a button for this you can also make a button for the other :)

    Quote from chente

    I'm used to joining certain containers on the same network in this way. I know it can be done from the same yaml file, but I find it more... easy? comfortable? It's just how I learned to do it and have continued to do it that way from CLI since I left Portainer months ago.

    Thats me to a tee, when I started from scratch with the compose plugin, I did do from CLI. Of course I suppose we'll also need a 'Delete Network' button and 'Leave Network' button as well. The Inspect button does a good job as it is.

    Quote from trythat

    Funnily enough thats why I stooped using gluetun, it would cause problems with other containers connecting to it, I changed to binhex's qbittorentvpn and his delugevpn, and if needed ran the other containers through 1 of those. It's worked well for quite some time, must admit I rather use gluetun, but needs must.

    Gluetun stopping other containers when the vpn disconnects is actually a feature not a bug. This is a reason I use it and also the easiest way to manage that is through a single yaml with multiple containers. But from reading the thread that doesn’t seem to be the dev preferred method so won’t really be supported in the new plug-in.


    Which is fine I can continue using portainer, just seems a little silly that everyone wants all the existing bells and whistles of portainer in the compose plug-in instead of just using portainer.

    • Official Post
    Quote from trythat

    Of course I suppose we'll also need a 'Delete Network' button and 'Leave Network' button as well.

    The problem I have with these buttons is that someone is going to click them on a network used by a running container and not know what they did.

    omv 6.9.0-1 Shaitan | 64 bit | 6.2 proxmox kernel

    plugins :: omvextrasorg 6.3.1 | kvm 6.2.16 | compose 6.10.3 | cputemp 6.1.3 | mergerfs 6.3.7


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Official Post
    Quote from Sixtas

    Any suggestion? I am a bit lost about this.

    The running task just means you closed your browser when something was running. You should be able to re-attach to it.


    Fixing the time should've fixed all of your issues that I saw. What is wrong now?

    omv 6.9.0-1 Shaitan | 64 bit | 6.2 proxmox kernel

    plugins :: omvextrasorg 6.3.1 | kvm 6.2.16 | compose 6.10.3 | cputemp 6.1.3 | mergerfs 6.3.7


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Official Post
    Quote from hoobatoo

    just seems a little silly that everyone wants all the existing bells and whistles of portainer in the compose plug-in instead of just using portainer.

    I prefer not to use Portainer for many reasons, here are some of them. https://wiki.omv-extras.org/do…se_openmediavault-compose

    If the plugin provides more functionality it will be more useful and will sometimes avoid going to the CLI, so I don't see the problem in this.

    Quote from ryecoaaron

    The running task just means you closed your browser when something was running. You should be able to re-attach to it.


    Fixing the time should've fixed all of your issues that I saw. What is wrong now?

    Ok sorry for not telling.

    I still have no option to install the compose plugin. And I still have the OMV5 Plugins in my plugins list, using OMV6 and having installed the OMV6 extras.

    I want to try to reacitvate my portainer containers but can't even start without the compose plugin :)

    Version: 6.5.4-1 (Shaitan)

    Kernel: Linux 6.1.0-0.deb11.7-amd64

    Edited 2 times, last by Sixtas ().

    Quote from trythat

    I like the Network tab, like you, I wouldn't mind a Network create, but again it's not a biggie as that's quite a bit extra to program in.

    I'd like a network create. I use it once per docker instance to create a user bridge for communication between named containers which the normal bridge does not provide.


    Per the docker documentation:  Containers on the default bridge network can only access each other by IP addresses, unless you use the --link option, which is considered legacy. On a user-defined bridge network, containers can resolve each other by name or alias.


    Maybe instead of extra buttons (create/delete) store all non compose files in some type of docker (shell?) command file? That could be a solution for everything which does not fit the compose format and yaml checks..

    • Official Post
    Quote from Sixtas

    I still have no option to install the compose plugin. And I still have the OMV5 Plugins in my plugins list, using OMV6 and having installed the OMV6 extras.

    I want to try to reacitvate my portainer containers but can't even start without the compose plugin

    Did you post the output of sudo omv-aptclean repos somewhere?

    omv 6.9.0-1 Shaitan | 64 bit | 6.2 proxmox kernel

    plugins :: omvextrasorg 6.3.1 | kvm 6.2.16 | compose 6.10.3 | cputemp 6.1.3 | mergerfs 6.3.7


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Official Post
    Quote from DjoeC

    Maybe instead of extra buttons (create/delete)

    I don't mind a create button since it can't really do any harm making another network.

    omv 6.9.0-1 Shaitan | 64 bit | 6.2 proxmox kernel

    plugins :: omvextrasorg 6.3.1 | kvm 6.2.16 | compose 6.10.3 | cputemp 6.1.3 | mergerfs 6.3.7


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    Quote from hoobatoo

    Gluetun stopping other containers when the vpn disconnects is actually a feature not a bug. This is a reason I use it and also the easiest way to manage that is through a single yaml with multiple containers. But from reading the thread that doesn’t seem to be the dev preferred method so won’t really be supported in the new plug-in.


    Which is fine I can continue using portainer, just seems a little silly that everyone wants all the existing bells and whistles of portainer in the compose plug-in instead of just using portainer.

    I know about the kill feature, but it's no good if my other containers come up before gluetun, and nearly all vpn container take a while to come up.

    Quote

    But from reading the thread that doesn’t seem to be the dev preferred method so won’t really be supported in the new plug-in.

    Are you on about the docker-compose plugin? There's nothing stopping you from having multiple images, I use nginx and that has a nginx image and a database image. I just think a lot of user's here like 1 image to 1 yml

    Quote from ryecoaaron

    Did you post the output of sudo omv-aptclean repos somewhere?

    Yeah I did in Post #630 but I can do it again. Just fresh.




    And strangely I have currently a returning Background Task Notification which occurs in *Connection lost* with following failure when I try to attach it...



    I don't know what is going on :(

    Version: 6.5.4-1 (Shaitan)

    Kernel: Linux 6.1.0-0.deb11.7-amd64

    Edited 2 times, last by Sixtas ().

    • Official Post
    Quote from Sixtas

    I don't know what is going on

    I do... Run these commands:


    sudo wget -O /usr/sbin/omv-mkaptidx https://github.com/openmediavault/openmediavault/raw/master/deb/openmediavault/usr/sbin/omv-mkaptidx

    sudo chmod +x /usr/sbin/omv-mkaptidx

    sudo omv-mkaptidx

    omv 6.9.0-1 Shaitan | 64 bit | 6.2 proxmox kernel

    plugins :: omvextrasorg 6.3.1 | kvm 6.2.16 | compose 6.10.3 | cputemp 6.1.3 | mergerfs 6.3.7


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    Quote from ryecoaaron

    The problem I have with these buttons is that someone is going to click them on a network used by a running container and not know what they did.

    be aware to convert the pluging on other "portainer".



    For me, actual features are enought.



    and thanks for your efforts.

    Quote from DjoeC

    I'd like a network create. I use it once per docker instance to create a user bridge for communication between named containers which the normal bridge does not provide.


    Per the docker documentation:  Containers on the default bridge network can only access each other by IP addresses, unless you use the --link option, which is considered legacy. On a user-defined bridge network, containers can resolve each other by name or alias.


    Maybe instead of extra buttons (create/delete) store all non compose files in some type of docker (shell?) command file? That could be a solution for everything which does not fit the compose format and yaml checks..

    I use a network named "my-net", only need to create first (one time) and use on all containers.



    How I do it:


    1 - deploy container using plugin

    2 - use portainer to create desired networks ( eg: my-net and MyMacVLAN)

    3 - go to pluging and edit portainer yaml file to use new created network my-net.

    4 - redeploy.


    Done.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login