Adding a terminal (cli) to OMV in general.

Now we have a cli allowing exec into docker containers.

Would it be possible to add the cli to use in OMV instead of having to ssh in?

If so, it would be nice if it was available at all times, so it could be placed in the same group as the user settings and power etc section.

I would assume it would use the currant user, and either enter at the home folder if there is one, or straight into /. It would be nice if it logged into the cli automatically as current user so no need to login as we do with compose plugin cli, also unlike how the compose plugin cli works, it would pop out a window.

To me, it looks as though the hard work has been done, but I'm not a developer, so I could and probably am talking rubbish, but if you don't ask you don't get.

Quote from bermuda

It's already possible. Use wetty plugin or install a wetty docker from examples.

Next time check the forum first.

I know wetty is available!

But it doesn't do what I was hoping for. In fact it's just as quick to use ssh, because of the number of clicks you need to access wetty, you still have to enter username and password, I would like a separate button as I said, and to be auto logged in. I don't see how you can auto login with wetty unless you know better?

If ryecoaaron say's he doesn't want to or it can't be done then so be it, but I put it out there, to see if anyone else thought the same as me. I don't mind either way, but for me OMV works best when I can do most things from within OMV, such compose and now being able to exec into a container.

As the exec function is a new addition to the compose plugin and seems a big advantage over using wetty or ssh, then I thought I ask.

If you're happy with wetty, then fine carry on using it.

Quote from raulfg3

you can configure wetty docker to autologon.

example:

Code

services:
  wetty:
    image: wettyoss/wetty:latest
    container_name: wetty
    cap_add:
      - NET_ADMIN
    environment:
      - SSHHOST=$SSHHOST
      - SSHPORT=$SSHPORT
      - SSHUSER=root
      - BASE=/
    ports:
      - 3000:3000
    restart: unless-stopped

Display More

more config:

https://hub.docker.com/r/wettyoss/wetty

Display More

Nice and thanks, didn't realise that. But you can't do that from the wetty plugin, so would need a container rather than a button where I'd like a button added, so sshing with keys would still be easier.

But thanks again.

Quote from ryecoaaron

The exec function of the compose plugin doesn't auto login either. And while the code could be adapted to the system, it would just be recreating wetty and not as good as wetty. I created the exec terminal for the compose plugin because nothing really existed that would work with the plugin.

Fair enough, I'll stick to ssh then.

Quote from bermuda

The point of wetty is to get a console to your host without a vpn or some port forwarding. You simply connect to it via http, which is already exposed to the internet.

And passwords are there for a reason. Nonetheless wetty **is** able to auto-login.

I don't expose to the internet.

But I suppose what it comes down to, is that I don't like wetty, so don't use it. If everyone else is happy using it, great, carry on, there is very rarely just one way of doing something with computing.

I'm ok with using ssh, it was just an idea. Not sure why people are getting so up tight about it.

Quote from bermuda

That's why.

Meaning what? Because I'd like an easier way of accessing a shell from within OMV. I'm having another look at this going forward.

I do use ssh with keys, but that wasn't the point.

Any way I've started another thread about using WeTTY, where I did a bit more thinking on the matter first. But it does look as though I'm in the minority about wanting shell access from the main menu of OMV like other NAS and Hypervisors - unfortunately.

But thats how it goes, you have an idea, and sometimes you're the only one who likes it.