Docker Diskover

A Docker container for the Diskover space mapping application
Alternatives To Docker Diskover
Project NameStarsDownloadsRepos Using ThisPackages Using ThisMost Recent CommitTotal ReleasesLatest ReleaseOpen IssuesLicenseLanguage
Portainer25,03318 hours ago78April 21, 20211,091zlibGo
Making Docker and Kubernetes management easy.
Awesome Docker24,728
6 days agoapache-2.0
:whale: A curated list of Docker resources and projects
5 days ago34mitDockerfile
Pre-Built Vulnerable Environments Based on Docker-Compose
7 months ago75mitDockerfile
Various Dockerfiles I use on the desktop and on servers.
Kaniko12,0621a day ago29August 10, 2022606apache-2.0Go
Build Container Images In Kubernetes
117 days ago66July 09, 2022139gpl-3.0Haskell
Dockerfile linter, validate inline bash, written in Haskell
Docker Node7,659
18 hours ago107mitDockerfile
Official Docker Image for Node.js :whale: :turtle: :rocket:
4 months ago109mitHTML
The last Markdown editor, ever.
V2ray For Doprax6,889
a day agoDockerfile
The tool can install v2ray on the Doprax, including VMess and VLess protocols, it will automatically switch IP, you need to fork this projects, read and run it. Create By ifeng.
Buildkit6,564592173 hours ago274August 22, 2022614apache-2.0Go
concurrent, cache-efficient, and Dockerfile-agnostic builder toolkit
Alternatives To Docker Diskover
Select To Compare

Alternative Project Comparisons

Blog Discord Discourse Fleet GitHub Open Collective

The team brings you another container release featuring:

  • regular and timely application updates
  • easy user mappings (PGID, PUID)
  • custom base image with s6 overlay
  • weekly base OS updates with common layers across the entire ecosystem to minimise space usage, down time and bandwidth
  • regular security updates

Find us at:

  • Blog - all the things you can do with our containers including How-To guides, opinions and much more!
  • Discord - realtime support / chat with the community and the team.
  • Discourse - post on our community forum.
  • Fleet - an online web interface which displays all of our maintained images.
  • GitHub - view the source for all of our repositories.
  • Open Collective - please consider helping us by either donating or contributing to our budget

linuxserver/diskover pulls GitHub Stars GitHub Release GitHub Package Repository GitLab Container Registry Docker Pulls Docker Stars Jenkins Build LSIO CI

diskover is an open source file system indexer that uses Elasticsearch to index and manage data across heterogeneous storage systems.


Supported Architectures

We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.

Simply pulling should retrieve the correct image for your arch, but you can also pull specific arch images via tags.

The architectures supported by this image are:

Architecture Available Tag
x86-64 amd64-<version tag>
arm64 arm64v8-<version tag>
armhf arm32v7-<version tag>

Application Setup

This application is dependent on an ElasticSearch instance. Please see the example compose file for additional information.

The default username is diskover with the password of darkdata, access the container at http://<host-ip>/. The UI may be unusable until a valid index has been created.

The default diskover-web Constants.php file located at /config/diskover-web.conf.d/Constants.php will need to be edited to allow diskover-web to communicate with the ElasticSearch container. The following entries will need to be edited:

  • const ES_HOST = elasticsearch
  • const ES_PORT = 9200

The application doesn't start an index by default. A crontab is created inside of the /config directory and can be set up to run automated indexes of /data. Changes to this crontab file require a restart to apply. You can also manually run an index by executing /app/diskover/ either in interactive or detached mode:

  • docker exec -u abc -d diskover python3 /app/diskover/ -i diskover-my_index_name /data Will run an index in the background
  • docker exec -u abc -it diskover python3 /app/diskover/ -i diskover-my_index_name /data Will run an index in the foreground


Here are some example snippets to help you get started creating a container.

docker-compose (recommended, click here for more info)

version: '2'
    container_name: diskover
      - PUID=1000
      - PGID=1000
      - TZ=America/New_York
      - ES_HOST=elasticsearch
      - ES_PORT=9200
      - /path/to/diskover/config:/config
      - /path/to/diskover/data:/data
      - 80:80
    mem_limit: 4096m
    restart: unless-stopped
      - elasticsearch
    container_name: elasticsearch
      - discovery.type=single-node
      - bootstrap.memory_lock=true
      - "ES_JAVA_OPTS=-Xms1g -Xmx1g"
        soft: -1
        hard: -1
      - /path/to/esdata:/usr/share/elasticsearch/data
      - 9200:9200
      - elasticsearch-helper
    restart: unless-stopped
    image: alpine
    command: sh -c "sysctl -w vm.max_map_count=262144"
    privileged: true

docker cli (click here for more info)

docker run -d \
  --name=diskover \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Etc/UTC \
  -e ES_HOST=elasticsearch \
  -e ES_PORT=9200 \
  -e ES_USER=elastic \
  -e ES_PASS=changeme \
  -p 80:80 \
  -v /path/to/diskover/config:/config \
  -v /path/to/diskover/data:/data \
  --restart unless-stopped \


Container images are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate <external>:<internal> respectively. For example, -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 outside the container.

Parameter Function
-p 80 diskover Web UI
-e PUID=1000 for UserID - see below for explanation
-e PGID=1000 for GroupID - see below for explanation
-e TZ=Etc/UTC specify a timezone to use, see this list.
-e ES_HOST=elasticsearch ElasticSearch host (optional)
-e ES_PORT=9200 ElasticSearch port (optional)
-e ES_USER=elastic ElasticSearch username (optional)
-e ES_PASS=changeme ElasticSearch password (optional)
-v /config Persistent config files
-v /data Default mount point to crawl

Environment variables from files (Docker secrets)

You can set any environment variable from a file by using a special prepend FILE__.

As an example:

-e FILE__PASSWORD=/run/secrets/mysecretpassword

Will set the environment variable PASSWORD based on the contents of the /run/secrets/mysecretpassword file.

Umask for running applications

For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional -e UMASK=022 setting. Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up here before asking for support.

User / Group Identifiers

When using volumes (-v flags) permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user PUID and group PGID.

Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.

In this instance PUID=1000 and PGID=1000, to find yours use id user as below:

  $ id username
    uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)

Docker Mods

Docker Mods Docker Universal Mods

We publish various Docker Mods to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.

Support Info

  • Shell access whilst the container is running: docker exec -it diskover /bin/bash
  • To monitor the logs of the container in realtime: docker logs -f diskover
  • container version number
    • docker inspect -f '{{ index .Config.Labels "build_version" }}' diskover
  • image version number
    • docker inspect -f '{{ index .Config.Labels "build_version" }}'

Updating Info

Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (ie. nextcloud, plex), we do not recommend or support updating apps inside the container. Please consult the Application Setup section above to see if it is recommended for the image.

Below are the instructions for updating containers:

Via Docker Compose

  • Update all images: docker-compose pull
    • or update a single image: docker-compose pull diskover
  • Let compose update all containers as necessary: docker-compose up -d
    • or update a single container: docker-compose up -d diskover
  • You can also remove the old dangling images: docker image prune

Via Docker Run

  • Update the image: docker pull
  • Stop the running container: docker stop diskover
  • Delete the container: docker rm diskover
  • Recreate a new container with the same docker run parameters as instructed above (if mapped correctly to a host folder, your /config folder and settings will be preserved)
  • You can also remove the old dangling images: docker image prune

Via Watchtower auto-updater (only use if you don't remember the original parameters)

  • Pull the latest image at its tag and replace it with the same env variables in one run:

    docker run --rm \
    -v /var/run/docker.sock:/var/run/docker.sock \
    containrrr/watchtower \
    --run-once diskover
  • You can also remove the old dangling images: docker image prune

Note: We do not endorse the use of Watchtower as a solution to automated updates of existing Docker containers. In fact we generally discourage automated updates. However, this is a useful tool for one-time manual updates of containers where you have forgotten the original parameters. In the long term, we highly recommend using Docker Compose.

Image Update Notifications - Diun (Docker Image Update Notifier)

  • We recommend Diun for update notifications. Other tools that automatically update containers unattended are not recommended or supported.

Building locally

If you want to make local modifications to these images for development purposes or just to customize the logic:

git clone
cd docker-diskover
docker build \
  --no-cache \
  --pull \
  -t .

The ARM variants can be built on x86_64 hardware using multiarch/qemu-user-static

docker run --rm --privileged multiarch/qemu-user-static:register --reset

Once registered you can define the dockerfile to use with -f Dockerfile.aarch64.


  • 02.03.23: - Set permissions on crontabs during init.
  • 20.08.22: - Rebasing to alpine 3.17 with php8.1. Restructure nginx configs (see changes announcement).
  • 25.02.22: - Add php7-sqlite3 to support rc4 release.
  • 03.11.21: - Added more support for potential config files.
  • 31.10.21: - Added variable to ElasticSearch; added instructions to edit Constants.php in diskover; corrected command needed to manually generate an index in diskover
  • 11.10.21: - Updated to diskover-community v2.
  • 19.11.20: - Fix pip packages.
  • 19.12.19: - Rebasing to alpine 3.11.
  • 28.06.19: - Rebasing to alpine 3.10.
  • 12.04.19: - Rebase to Alpine 3.9.
  • 23.03.19: - Switching to new Base images, shift to arm32v7 tag.
  • 01.11.18: - Initial Release.
Popular Docker Projects
Popular Dockerfile Projects
Popular Virtualization Categories

Get A Weekly Email With Trending Projects For These Categories
No Spam. Unsubscribe easily at any time.