Compose plugin exec feature

trythat · May 21st 2025

Code

Ohhhh, I didn't know you meant the containers list on the terminal list. No, it is not sortable. Why would it need to be? The containers are sortable and filterable from the Containers tab and Services tab in the plugin and will open the terminal directly. I just added the container list to the terminal site for testing. It wasn't really meant to be flexible.

I don't need an option to resort the container list. I just assumed that the list would be sorted when displayed, it's not a biggy, just a thing I think makes it easy to find the next container you need to exec into.

But I suppose when using the exec function when not testing, perhaps removing the container button is the better option.

trythat · May 21st 2025

Just a question - I do most of my work from the Files tab, would it be possible to add this option to that tab?

ryecoaaron · May 21st 2025

Quote from trythat

just a thing I think makes it easy to find the next container you need to exec into.

That is literally what the Services tab is for. I don't see the difference.

Quote from trythat

But I suppose when using the exec function when not testing, perhaps removing the container button is the better option.

Because the list isn't sorted? I am going to leave it because it provides a landing page if someone exits out of the terminal. I will look at sorting the list.

Quote from trythat

would it be possible to add this option to that tab?

Since a file could be multiple containers, how would the plugin know what container to exec into?

ryecoaaron · May 21st 2025

list will be sorted now - https://github.com/OpenMediaVa…424adc1ad14976fcfd4bc8282

raulfg3 · May 21st 2025

sorry , not sure how to use exec funtion, some screen capture are welcome.

Thanks.

ryecoaaron · May 21st 2025

Quote from raulfg3

not sure how to use exec funtion, some screen capture are welcome.

most users won't have a need for it.

You need to enable it at the bottom of the Settings tab. Then Apply changes.

You will need a user to be in the "dockerterm" group that is created by the plugin. You can do that from the OMV Users tab.

The Services and Containers tab will have a "Terminal Link" column. Click on it to go to the terminal. If you haven't signed in, it will ask you to do that.

trythat · May 21st 2025

Quote from ryecoaaron

list will be sorted now - https://github.com/OpenMediaVa…424adc1ad14976fcfd4bc8282

Thank you.

trythat · May 21st 2025

Quote from ryecoaaron

Since a file could be multiple containers, how would the plugin know what container to exec into?

Hadn't thought of that. Good explanation.

trythat · May 21st 2025

ryecoaaron I've looked at the compose files and made some changes, how can I get the zip file to you? I have sent files to you before, but I can't remember how

If you don't want them, thats fine, but I was surprised at how many of them had changed.

ryecoaaron · May 21st 2025

You attached them to a PM before.

ryecoaaron · May 22nd 2025

7.5.1 is in the repo. Sorts the container names and fixes the terminal column/line wrap problem

raulfg3 · May 22nd 2025

sorry but do not work for me, I use port 6000 because one docker use port 5000, but exec do not work:

exec try to connect to: https://bdns.local:6000/terminal/heimdall

jata1 · May 22nd 2025

ryecoaaron - massive thanks for this addition to compose plugin.

Working great on all my containers except dozzle on both my minipc and rpi.

error message with dozzle is below.

awesome work!

Code

CI runtime exec failed: exec failed: unable to start container process: exec: "sh": executable file not found in $PATH: unknown

ryecoaaron · May 22nd 2025

Quote from jata1

Working great on all my containers except dozzle on both my minipc and rpi.

error message with dozzle is below.

dozzle must not have sh or bash available. I guess I could add another shell but that is very strange that it doesn't have sh. I guess it might not have it in the PATH and I could call /bin/sh instead. When you exec into the container normally, what do you use?

jata1 · May 22nd 2025

I have never tried or needed to exec into dozzle so just reporting from my testing.

Dozzle has a similar tool/feature to get to shell / cli for containers. I tried this on the dozzle container and it didn’t work either.

So I think you are right there is no bash or sh for dozzle.

trythat · May 22nd 2025

Quote from ryecoaaron

dozzle must not have sh or bash available. I guess I could add another shell but that is very strange that it doesn't have sh. I guess it might not have it in the PATH and I could call /bin/sh instead. When you exec into the container normally, what do you use?

Just tested dozzle via ssh and you are correct, it doesn't seem to work with bash or sh, whether it's preceded by bin.

raulfg3 · May 23rd 2025

Quote from raulfg3

sorry but do not work for me, I use port 6000 because one docker use port 5000, but exec do not work:

exec try to connect to: https://bdns.local:6000/terminal/heimdall

What can I check to revise why is not working?

ryecoaaron · May 23rd 2025

Quote from raulfg3

What can I check to revise why is not working?

What isn't working? I suppose I should add a status for the service.

sudo systemctl status omv_compose_term

raulfg3 · May 23rd 2025

Quote from ryecoaaron

What isn't working? I suppose I should add a status for the service.

sudo systemctl status omv_compose_term

thanks , this is the output:

Code

root@bdns:~# sudo systemctl status omv_compose_term
● omv_compose_term.service - Docker exec terminal for openmediavault-compose
     Loaded: loaded (/etc/systemd/system/omv_compose_term.service; enabled; preset: enabled)
     Active: active (running) since Thu 2025-05-22 07:30:02 CEST; 1 day 10h ago
   Main PID: 53007 (python3)
      Tasks: 1 (limit: 9334)
     Memory: 29.4M
        CPU: 12.540s
     CGroup: /system.slice/omv_compose_term.service
             └─53007 /usr/bin/python3 /opt/omv_compose_term/omv_compose_term.py

may 22 07:30:02 bdns systemd[1]: Started omv_compose_term.service - Docker exec terminal for openmediavault-compose.
may 22 07:30:02 bdns python3[53007]: WebSocket transport not available. Install simple-websocket for improved performance.
may 22 07:30:02 bdns python3[53007]: Werkzeug appears to be used in a production deployment. Consider switching to a production web server i>
may 22 07:30:02 bdns python3[53007]:  * Serving Flask app 'omv_compose_term'
may 22 07:30:02 bdns python3[53007]:  * Debug mode: off

root@bdns:~#

Display More

ryecoaaron · May 23rd 2025

The service is running. I would guess your dns isn't working for the hostname in the url? What happens if you use the same url for OMV but add port 6000?

Compose plugin exec feature

Participate now!

Similar Threads

OMV7 compose - saving a compose file spins up unrelated disks by df