lscr.io/linuxserver/diskover:latest
should retrieve the correct image for your arch, but you can also pull specific arch images via tags.http://<host-ip>/
. The UI may be unusable until a valid index has been created./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
/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/diskover.py
either in interactive or detached mode:docker exec -u abc -d diskover python3 /app/diskover/diskover.py -i diskover-my_index_name /data
Will run an index in the backgrounddocker exec -u abc -it diskover python3 /app/diskover/diskover.py -i diskover-my_index_name /data
Will run an index in the foreground<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.-p
)80
-e
)PUID=1000
PGID=1000
TZ=America/New_York
ES_HOST=elasticsearch
ES_PORT=9200
ES_USER=elastic
ES_PASS=changeme
-v
)/config
/data
FILE__
.PASSWORD
based on the contents of the /run/secrets/mysecretpassword
file.-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.-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
.PUID=1000
and PGID=1000
, to find yours use id user
as below:docker exec -it diskover /bin/bash
docker logs -f diskover
docker inspect -f '{{ index .Config.Labels "build_version" }}' diskover
docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/diskover:latest