The one you want to use for the shell. Do not use a system user. Use a user you created in OMV. You can also create a new user.
To create a new user was also my idea now. To which groups should this user belong and to which folders should it have access rights?
groups cterm and sudo (if you want to run commands with elevated privileges)
you do not have to grant access to any folders, unless you want to use the same user for services like samba
To create a new user was also my idea now. To which groups should this user belong and to which folders should it have access rights?
This is my settings for user trythat.
_ssh, adm, audio, cdrom, cterm, dip, docker, floppy, kvm, netdev, openmediavault-admin, plugdev, sudo, trythat, users, videoBut I did this a while ago, I realize some of these are not needed. Default OMV groups is 'users', but this is a minimum I would think.
If using ssh - _ssh
if using docker - docker
if using kvm - kvm
if using sudo - sudo
username - username
if using cterm - cterm
default group - users
The following are my linux laptop user groups, as default,
uid=1000(trythat) gid=1000(trythat) groups=1000(trythat),4(adm),20(dialout),21(fax),24(cdrom),25(floppy),26(tape),27(sudo),29(audio),30(dip),44(video),46(plugdev),100(users),106(netdev),110(lpadmin),115(bluetooth),123(scanner)So I suppose this might be a starting point until someone comes up with a better answer.
I have reduced it now to cterm, root, sudo, users. This should be enough for CTerm.
Why "root" group? Dangerous
"root" and "sudo" does not make sense
Users created in the GUI of OMV are members of the users group by default.
Why "root" group? Dangerous
"root" and "sudo" does not make sense
To be able to start system commands on the host like in the SSH shell.
And you also told to include "sudo" some post before. 
... but for testing the new plugin I also reduced to "cterm, users".
Display MoreIt is short for Compose Exec Terminal (new feature in the Compose plugin). That was too long for the services status so I named it CTerm for short.
https://github.com/OpenMediaVa…/main/debian/changelog#L3
You can't.
Aside from the lack of inclusion in the official documentation (+wiki), this is how I feel about it: I'm Lovin' It.
Aside from the lack of inclusion in the official documentation (+wiki)
It is still developing.
And you also told to include "sudo" some post before.
Yep, but I would never tell anybody to add a user to the root group.
I tell people to never add a user to the root group.
Cterm --> nice add-on. I just have a MariaDB and Sonarr running in OMV and do not see any practical reason for using it. If and when I need to get on OMV CLI I just ssh to it from one of my Linux computers. Maybe I am missing something, so if anyone would give me an example of practical use of it, I would greatly appreciate.
nice add-on. I just have a MariaDB and Sonarr running in OMV and do not see any practical reason for using it. If and when I need to get on OMV CLI I just ssh to it from one of my Linux computers. Maybe I am missing something, so if anyone would give me an example of practical use of it, I would greatly appreciate.
You don't have to force yourself to use it. It is not meant to be wetty. It is an easy way to exec into a docker container (portainer has this feature) and get an LXC console (proxmox has this feature). The host terminal was added because it was easy.
I exec into mysql containers at work because no user has privileges to change schema and root can't login. Keeps the database secure.
You don't have to force yourself to use it. It is not meant to be wetty. It is an easy way to exec into a docker container (portainer has this feature) and get an LXC console (proxmox has this feature). The host terminal was added because it was easy.
I exec into mysql containers at work because no user has privileges to change schema and root can't login. Keeps the database secure.
It is, really, not a question of being "forced" to use it. Month or so ago I had a catastrophic failure of the drive holding MariaDB databases that I use for 5 Kodi installs. If this have happen right now the CTerm would be great to create actual Kodi user, using "mysql -u root -p" and then "CREATE USER 'kodi' IDENTIFIED BY 'kodi'; ", and permission in MariaDB. Instead I had to install Portainer. Worked great. Yes "root" cannot login and I am the only person accessing it. This is my home intranet.
What is the difference of cterm in comparison to ssh connection dropping "docker exec -it --user xy mycontainer bash" and whatever is needed?
What is the difference of cterm in comparison to ssh connection dropping "docker exec -it --user xy mycontainer bash" and whatever is needed?
no difference really as far as I can see. Just a web gui way to access the containers shells instead of via an ssh connection.
What is the difference of cterm in comparison to ssh connection dropping "docker exec -it --user xy mycontainer bash" and whatever is needed?
The same except it doesn't pass the user parameter. https://github.com/OpenMediaVa…v_cterm/omv_cterm.py#L712
It does connect to LXC containers and can be a host shell too.
But nothing magic here. This was pretty much the last feature from portainer and proxmox that I thought the compose and kvm plugins needed.
But nothing magic here. This was pretty much the last feature from portainer and proxmox that I thought the compose and kvm plugins needed.
Giving that OMV moved away from Portainer and moved to Compose, it only make sense to complete transition and implement last features from Portainer and Proxmox.
is there anyway to put a hold on the cterm plugin?
unable to achieve it for some reason
is there anyway to put a hold on the cterm plugin?
What does this mean?
What does this mean?
I uninstalled cterm which was reinstalled with a compose update.
just now tried to put a hold both via dpkg and the apt tool plugin and was unable to do so
Don’t have an account yet? Register yourself now and be a part of our community!
