Portainer Templates logo

Portainer Templates

Cloud Commander Cloud Commander

Container

DocumentsNetwork OtherTools

Cloud Commander a file manager for the web with console and editor.

Image details

Pulls: 88.3M
Architecture: amd64, arm64
Image size: 189 MB
Latest: 19.20.0-slim
User: coderaiser
Created: Dec 09, 2015
Updated: 9 days ago
Status: active

Source details

Repo: coderaiser/cloudcmd
Stars: 2k
Forks: 266
Language: JavaScript
License: MIT
Latest: v19.20.0 · 9 days ago
Updated: 9 days ago
Website: cloudcmd.io/

Configuration

Type
Container
Image
coderaiser/cloudcmd
Ports
8000/tcp
Volumes
/media/host/opt/mediadepot : /opt/mediadepot/apps/media/host/media/storage : /media/storage/media/host/media/temp : /media/temp
Labels
traefik.enable=truetraefik.http.services.cloudcmd.loadbalancer.server.port=8000traefik.http.routers.cloudcmd.entrypoints=websecuretraefik.http.routers.cloudcmd.tls.certresolver=mydnschallengetraefik.http.routers.cloudcmd.middlewares=authmetraefik.http.middlewares.authme.forwardauth.address=http://authelia:9091/api/verify?rd=https://login.${DEPOT_DOMAIN_NAME}/traefik.http.middlewares.authme.forwardauth.trustforwardheader=true

Template by mediadepot

Standalone Install

Select an install method, to see config/commands for deploying Cloud Commander

Installation method

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select Cloud Commander, fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo

More install options in our documentation, or see coderaiser/cloudcmd for app-specific guidance.

Cloud Commander !Build StatusBuildStatusIMGURLBuildStatusURL !CodacyCodacyIMGCodacyURL !GitterGitterIMGURLGitterURL

MainMainURL BlogBlogURL

Cloud Commander a file manager for the web with console and editor.
Cloud Commander
The docker images are provided for multiple architectures and types. The following list shows all existing images:
ArchitectureType
amd64linux
arm/v7linux
arm64 (arm/v8)linux
amd64linux-alpine
arm/v7linux-alpine
arm64 (arm/v8)linux-alpine

Cloud Commander could be used as a docker container this way:
docker run -it --rm -v ~:/root -v /:/mnt/fs -w=/root -p 8000:8000 coderaiser/cloudcmd

Config would be read from home directory, hosts root file system would be mount to /mnt/fs, 8000 port would be exposed to hosts port.
Also you could use docker compose with docker-compose.yml:
version: '2'
services:
  web:
    ports:
      - 8000:8000
    volumes:
      - ~:/root
      - /:/mnt/fs
    image: coderaiser/cloudcmd

When you create this file run:
docker-compose up

Documentation

More documentation you can find on https://cloudcmd.io/.

Get involved

There is a lot ways to be involved in Cloud Commander development:

License

MIT

Serve Cloud Commander on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.

Proxying cloud-commander.example.com to http://cloudcmd:8000

Add this to your Caddyfile

cloud-commander.example.com {
	reverse_proxy http://cloudcmd:8000
}

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

  • In Portainer, go to Containers, click the container, then Logs. Or run docker logs cloudcmd
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Published on a random port

This template exposes 8000/tcp without setting a host port, so Docker picks a random free one on every deploy.

  • Find it in the Ports column of Portainer's container list, or with docker port cloudcmd

Permission denied on volumes

If the logs show "permission denied", the app can't write to its data folder on the host.

  • Fix the ownership: sudo chown -R 1000:1000 /opt/mediadepot/apps (and the same for the other mapped folders)

Image won't pull

Test the pull directly on the host: docker pull coderaiser/cloudcmd

  • "manifest unknown" means the tag no longer exists. This template uses latest, so try pinning a specific version instead.
  • "toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
  • "no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

  • This image supports: amd64, arm64
  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

A single container

Cloud Commander runs as one container, the simplest kind of app here. Just the one image to pull and nothing else wired up alongside it.

The app image

An image is the app packed up ready to go, everything Cloud Commander needs bundled into one download. This template pulls coderaiser/cloudcmd, which Docker fetches once (about 189 MB) and then starts your own copy from.

Where the image comes from

Docker pulls its images from registries, public libraries of ready-built apps. Cloud Commander's comes from Docker Hub, published by coderaiser.

Version tags

The bit after the colon in the image name is the version tag. Here it's latest, which always points at the newest build, so a redeploy can bump you to a newer release without you asking. Newest right now is 19.20.0-slim. Pin a specific tag if you would rather stay on one version.

Which machines it runs on

Every image is built for particular CPU types. This one ships for amd64, arm64, so it runs on both regular x86 servers and ARM boards like a Raspberry Pi.

Ports

A port is the door the app answers on. Here the app exposes a port but leaves the host side blank, so Docker picks a free one for you. It opens:

  • 8000, published on a random host port

Volumes

A volume is where Cloud Commander keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:

  • /media/host/opt/mediadepot from /opt/mediadepot/apps on the host
  • /media/host/media/storage from /media/storage on the host
  • /media/host/media/temp from /media/temp on the host

Networking

Nothing custom is set, so Cloud Commander sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.

Container name

Once it's deployed, Portainer names the container cloudcmd. That's what you'll spot in the containers list and use in commands like docker logs cloudcmd.

Labels

Labels are small notes pinned to the container. They don't change how Cloud Commander behaves, but other tools read them, most often a reverse proxy like Traefik working out which apps to route where. This template sets:

  • traefik.enable=true
  • traefik.http.services.cloudcmd.loadbalancer.server.port=8000
  • traefik.http.routers.cloudcmd.entrypoints=websecure
  • traefik.http.routers.cloudcmd.tls.certresolver=mydnschallenge
  • traefik.http.routers.cloudcmd.middlewares=authme
  • traefik.http.middlewares.authme.forwardauth.address=http://authelia:9091/api/verify?rd=https://login.${DEPOT_DOMAIN_NAME}/
  • traefik.http.middlewares.authme.forwardauth.trustforwardheader=true

Open source license

Cloud Commander is open source, released under the MIT license. In plain terms the code is out in the open, so you're free to run it and change it to fit what you need.

Portainer app templates

Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Cloud Commander up. Add the template list to Portainer once, then deploying Cloud Commander is a click rather than a wall of config.