Portainer Templates logo

Portainer Templates

Diskover (stack) Diskover (stack)

Files

Open-source file indexer, search engine, data analytics and management platform powered by Elasticsearch.

Configuration

Type
Compose
Platform
linux
Source
Repo

Template by xneo1·Source

Services

elasticsearch

Configuration

Image
elasticsearch:7.17.10
Volumes
/usr/share/elasticsearch/data : /portainer/Files/AppData/Config/diskover/es_data
Env vars
discovery.type=single-nodexpack.security.enabled=falseES_JAVA_OPTS=-Xms512m -Xmx512m
Restart
unless-stopped

Image details

Pulls: 967.0M
User: stackbrew
Created: Feb 06, 2015
Updated: 4 days ago
Status: active

diskover

Configuration

Image
linuxserver/diskover:latest
Ports
8884:80
Volumes
/data : /mnt/MYSMBMOUNT/config : /portainer/Files/AppData/Config/diskover/data
Env vars
PUID=1000PGID=1000TZ=Europe/Athens
Restart
unless-stopped

Image details

Pulls: 6.1M
User: linuxserver
Created: Nov 12, 2018
Updated: 18 days ago
Status: active

Installation

  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 the app you wish to deploy, fill in any config options, and hit Deploy

Template Import URL

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

Service #1 - elasticsearch

docker run -d --name elasticsearch \
  -e 'discovery.type=single-node' \
  -e 'xpack.security.enabled=false' \
  -e 'ES_JAVA_OPTS=-Xms512m -Xmx512m' \
  -v /portainer/Files/AppData/Config/diskover/es_data:/usr/share/elasticsearch/data \
  --restart=unless-stopped \
  elasticsearch:7.17.10

Service #2 - diskover

docker run -d --name diskover \
  -p 8884:80 \
  -e 'PUID=1000' \
  -e 'PGID=1000' \
  -e 'TZ=Europe/Athens' \
  -v /mnt/MYSMBMOUNT:/data \
  -v /portainer/Files/AppData/Config/diskover/data:/config \
  --restart=unless-stopped \
  linuxserver/diskover:latest

If the stack expects env vars, set them or add them to a .env file first.

#PREREQUISITES
#Run below commands BEFORE DEPLOYING
#sudo chown -R 1000:1000 /portainer/Files/AppData/Config/diskover/es_data
#sudo sysctl -w vm.max_map_count=262144
#----------#
#Run initial crawl after deploy with: python3 /app/diskover/diskover.py /data

services:
  elasticsearch:
    image: elasticsearch:7.17.10
    container_name: elasticsearch    # Must be this!
    user: "1000:1000"
    environment:
      - discovery.type=single-node
      - xpack.security.enabled=false
      - "ES_JAVA_OPTS=-Xms512m -Xmx512m"
    volumes:
      - /portainer/Files/AppData/Config/diskover/es_data:/usr/share/elasticsearch/data
    restart: unless-stopped

  diskover:
    image: linuxserver/diskover:latest
    container_name: diskover
    ports:
      - "8884:80"
    volumes:
      - /mnt/MYSMBMOUNT:/data:ro
      - /portainer/Files/AppData/Config/diskover/data:/config
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/Athens
    depends_on:
      - elasticsearch
    restart: unless-stopped

Or, use the original compose file, straight from the template repo. Deploy with:

git clone https://github.com/xneo1/portainer_templates
cd portainer_templates
docker compose -f Template/Stack/diskover.yml up -d

For more installation options, see the Documentation in our GitHub repo

Container Documentation

elasticsearch Documentation

Elasticsearch is a powerful open source search and analytics engine that makes data easy to explore.

diskover Documentation

Serve Diskover (stack) 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 diskover-stack.example.com to http://diskover:80

Add this to your Caddyfile

diskover-stack.example.com {
	reverse_proxy http://diskover:80
}

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 <container>
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Port already in use

If deployment fails with "Bind for 0.0.0.0:8884 failed: port is already allocated", something else on your server is using that port.

  • Find what's using it: sudo ss -tlnp | grep :8884
  • Stop the other service, or pick a different host port. In 8884:80 only the left number is yours to change, the right one belongs to the app.

Running but the page won't load

The container is up but nothing appears in your browser.

  • Use your server's real IP: http://your-server-ip:8884. The 0.0.0.0 link Portainer shows isn't a real address.
  • Give it a minute after first deploy, diskover can take a while to initialise.
  • Make sure your firewall allows the port, e.g. sudo ufw allow 8884

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 /portainer/Files/AppData/Config/diskover/es_data (and the same for the other mapped folders)
  • Or set the PUID and PGID variables (defaults 1000:1000) to match your own user, found with id $USER

Image won't pull

Test the pull directly on the host: docker pull elasticsearch:7.17.10

  • "manifest unknown" means the tag no longer exists.
  • "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.

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

Container keeps restarting

The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.

  • Check the logs right after a restart, the last few lines before it died are the useful ones.
  • Get the exit code with docker inspect <container> --format '{{.State.ExitCode}}'
  • Still stuck? Redeploy once with the restart policy set to no so the failure stays visible.

Stack won't deploy

Compose stacks fail fast on small mistakes, and Portainer shows the reason just above the editor.

  • YAML only accepts spaces for indentation, a single tab breaks the whole file.

Raise an issue

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

Similar apps

Filegator Filegator FilesFilestash Filestash Files