OpenMediaVault - CloudCommander as Portainer.io Stack - Change username and password

Quote from GreyzardBigME

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.

Cloud Commander (cloudcmd.io)

And port 8000 will conflict with portainer:

version: '2'
services:
  web:
    ports:
      - 8000:8000
    volumes:
      - ~:/root
      - /:/mnt/fs
    image: coderaiser/cloudcmd

Quote from GreyzardBigME

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.

Quote from GreyzardBigME

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

Maybe one could think if you really need to mount the whole root file sysem

    volumes:
      - ~:/root
      - /:/mnt/fs

I would try

    volumes:
      - ~:/root 
     - /srv/dev-by-.../...:/mnt/fs

Quote from Zoki

I would try

Code

    volumes:
      - ~:/root 
     - /srv/dev-by-.../...:/mnt/fs

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.

Quote from GreyzardBigME

so, it's better to leave everything as is?

See below:

Quote from Frepke

You can set login credentials in cloudcommander, just press F10

Quote from GreyzardBigME

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.