hotio/hdidle
Starting the container¶
CLI:
docker run --rm \
--name hdidle \
--privileged=true \
-e PUID=1000 \
-e PGID=1000 \
-e UMASK=002 \
-e TZ="Etc/UTC" \
-e ARGS="" \
-e DEBUG="no" \
-e IDLE_TIME=1800 \
-v /<host_folder_config>:/config \
hotio/hdidle
Compose:
version: "3.7"
services:
hdidle:
container_name: hdidle
image: hotio/hdidle
privileged: true
environment:
- PUID=1000
- PGID=1000
- UMASK=002
- TZ=Etc/UTC
- ARGS
- DEBUG=no
- IDLE_TIME=1800
volumes:
- /<host_folder_config>:/config
Tags¶
Tag | Upstream | Version | Build |
---|---|---|---|
release (latest) |
GitHub releases |
You can also find tags that reference a commit or version number.
Executing your own scripts¶
If you have a need to do additional stuff when the container starts or stops, you can mount your script with the volume /docker/host/my-script.sh:/etc/cont-init.d/99-my-script
to execute your script on container start or /docker/host/my-script.sh:/etc/cont-finish.d/99-my-script
to execute it when the container stops. An example script can be seen below.
#!/usr/bin/with-contenv bash
echo "Hello, this is me, your script."
Troubleshooting a problem¶
By default all output is redirected to /dev/null
, so you won't see anything from the application when using docker logs
. Most applications write everything to a log file too. If you do want to see this output with docker logs
, you can set DEBUG
to yes
.