i've installed openmediavault on my raspberry pi alongside qbittorrent and cloudcommander as portainer.io stacks, how do i change the username and password of cloudcommander? everything works fine, i just need to change this last login credentials
OpenMediaVault - CloudCommander as Portainer.io Stack - Change username and password
-
-
how do i change the username and password of cloudcommander?
Which image are you using?
If it's the coderaiser/cloudcmd it should be running as root (big mistake if you have it open to the Internet)
The standard root path is host's / ,which means the complete system is wide open.
To have a different user and password (don't know if it's possible on Docker), you can try set a start command:
cloudcmd --username <a name> --password <a password> on the container configuration.
And port 8000 will conflict with portainer:
-
Your stack matches the one I deployed, except for "ports", where I have 7000:8000 instead of 8000:8000, I start this stack only when needed and stop it for the rest of the time, when I go to the web interface I'm automatically logged in
-
Your stack matches the one I deployed, except for "ports", where I have 7000:8000 instead of 8000:8000,
That's not my stack, it's the "default" from the Official page.
when I go to the web interface I'm automatically logged in
As root, I presume?
So, for what reason do you want to login with a different user?
The way it's built (the stack/container) is supposed to be ran this way.
-
You can set login credentials in cloudcommander, just press F10
-
-
That would be one approach to it but I believe that that container is intended for full outside control of the system's FS.
But, even with the "root" on a sub-folder of the FS, you're still running it as root, so you can always excalate to upper levels (maybe I'm wrong)
For me, it's an invitation to disaster.
-
so, it's better to leave everything as is? i dont use cloudcommander very often (but it's still useful) is it enough to stop the stack when not needed?
-
so, it's better to leave everything as is?
See below:
You can set login credentials in cloudcommander, just press F10
is it enough to stop the stack when not needed?
If you stop the container, you stop/kill the access to / (rootfs) via docker.
So, yes, it is enough,
Just be aware that, while "playing" with that container, you can simply kill your system.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!