Portainer Templates logo

Portainer Templates

Droppy Droppy

Container

ToolsNetwork WebNetwork Other

Droppy is a self-hosted file storage server

Image details

Pulls: 14.4M
Architecture: amd64, arm64, arm/v7, arm/v6
Image size: 45 MB
Latest: 12.2.0
User: silverwind
Created: Jan 03, 2016
Updated: 5 years ago
Status: active

Source details

Repo: silverwind/droppy
Stars: 2k
Forks: 187
Language: JavaScript
License: BSD-2-Clause
Latest: 12.2.0 · 5 years ago
Updated: 5 years ago
Status: archived

Configuration

Type
Container
Image
silverwind/droppy:latest
Ports
8989/tcp
Volumes
/files/tvshows : /media/storage/tvshows/files/movies : /media/storage/movies/files/music : /media/storage/music/files/photos : /media/storage/photos/files/ebooks : /media/storage/ebooks/files/documents : /media/storage/documents/files/software : /media/storage/software/files/downloads : /media/storage/downloads/files/blackhole : /media/temp/blackhole/files/processing : /media/temp/processing/config : /opt/mediadepot/apps/droppy
Env vars
GID=15000UID=15000TZ=America/Los_Angeles
Labels
traefik.enable=truetraefik.http.services.droppy.loadbalancer.server.port=8989traefik.http.routers.droppy.entrypoints=websecuretraefik.http.routers.droppy.tls.certresolver=mydnschallenge

Template by mediadepot

Standalone Install

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

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 Droppy, 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 silverwind/droppy for app-specific guidance.

See the README for more information.

Serve Droppy 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 droppy.example.com to http://droppy:8989

Add this to your Caddyfile

droppy.example.com {
	reverse_proxy http://droppy:8989
}

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 droppy
  • 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 8989/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 droppy

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 /media/storage/tvshows (and the same for the other mapped folders)

Image won't pull

Test the pull directly on the host: docker pull silverwind/droppy:latest

  • "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, arm/v7, arm/v6
  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Upstream project is archived

The developers have archived silverwind/droppy, so bugs and security issues won't be fixed.

  • It'll keep working for now, but consider the similar apps below for a maintained alternative.

Raise an issue

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

A single container

Droppy 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 Droppy needs bundled into one download. This template pulls silverwind/droppy:latest, which Docker fetches once (about 45 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. Droppy's comes from Docker Hub, published by silverwind.

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 12.2.0. 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, arm/v7, arm/v6, 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:

  • 8989, published on a random host port

Volumes

A volume is where Droppy 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:

  • /files/tvshows from /media/storage/tvshows on the host
  • /files/movies from /media/storage/movies on the host
  • /files/music from /media/storage/music on the host
  • /files/photos from /media/storage/photos on the host
  • /files/ebooks from /media/storage/ebooks on the host
  • /files/documents from /media/storage/documents on the host
  • /files/software from /media/storage/software on the host
  • /files/downloads from /media/storage/downloads on the host
  • /files/blackhole from /media/temp/blackhole on the host
  • /files/processing from /media/temp/processing on the host
  • /config from /opt/mediadepot/apps/droppy on the host

Environment variables

Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Droppy takes 3 of them, all with defaults you can leave alone or tweak:

  • GID, defaults to 15000
  • UID, defaults to 15000
  • TZ, defaults to America/Los_Angeles

Networking

Nothing custom is set, so Droppy 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 droppy. That's what you'll spot in the containers list and use in commands like docker logs droppy.

Labels

Labels are small notes pinned to the container. They don't change how Droppy 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.droppy.loadbalancer.server.port=8989
  • traefik.http.routers.droppy.entrypoints=websecure
  • traefik.http.routers.droppy.tls.certresolver=mydnschallenge

Open source license

Droppy is open source, released under the BSD-2-Clause 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 Droppy up. Add the template list to Portainer once, then deploying Droppy is a click rather than a wall of config.