Tommy's Notes Repository

whats up docker

2 min read

ignore this section:

Now that debian auto updates, I want to setup updates for paperless, so we are going to use What’s Up Docker. I’m choosing whats up docker almost purely because it has a REST API and a webui both of which allow me to just make an easy button to update paperless at any time. It also can send out notifications via a number of sources ( Smtp, Apprise, Ifttt, Pushover, Slack, Telegram, Discord )

I installed it using docker compose, with a compose file in /home/fcc/whatsupdocker.

version: '3'
 
services:
  whatsupdocker:
    image: getwud/wud
    container_name: wud
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    ports:
      - 3000:3000

this makes the whatsupdocker webui accessible on port 3000. I did not setup https.

I also set a user and a password in that compose file, but will obviously not be including them in this public facing documentation.

usernames and passwords are supplied via environment variables, like:

version: '3'

services:
  whatsupdocker:
    image: getwud/wud
    ...
    environment:
      - WUD_AUTH_BASIC_JOHN_USER=john
      - WUD_AUTH_BASIC_JOHN_HASH=$$apr1$$8zDVtSAY$$62WBh9DspNbUKMZXYRsjS/
      - WUD_AUTH_BASIC_JANE_USER=jane
      - WUD_AUTH_BASIC_JANE_HASH=$$apr1$$5iyu65pm$$m/6I35fjUT7.1CMnS2w9d1
      - WUD_AUTH_BASIC_BOB_USER=bob
      - WUD_AUTH_BASIC_BOB_HASH=$apr1$$aefKbZEa$$ZSA5Y3zv9vDQOxr283NGx/

and the passwords themselves are just hashes. they are NOT your password in plaintext.

to generate the hash of a password, you run

htpasswd -nib myuser mypassword

what’s up docker also supports oidc, so, if i setup authentik, or if i setup google for oidc, then that would be a great way to handle logins to wud.

now i must configure what’s up docker to actually do updating

this is done via triggers https://getwud.github.io/wud/#/configuration/triggers/docker-compose/

example for updating wud itself:

version: '3'

services:
  whatsupdocker:
    image: getwud/wud
    ...
    volumes:
    - /home/fcc/whatsupdocker/docker-compose.yml:/wud/wud/docker-compose.yml
    - /home/fcc/paperless-ngx/docker-compose.yml:/wud/paperless-ngx/docker-compose.yml
    environment:
      - WUD_TRIGGER_DOCKERCOMPOSE_WUD_FILE=/wud/wud/docker-compose.yml
      - WUD_TRIGGER_DOCKERCOMPOSE_PAPERLESSNGX_FILE=/wud/paperless-ngx/docker-compose.yml

so this is the whats up docker compose file i ended with:

version: '3'

services:
  whatsupdocker:
    image: getwud/wud
    container_name: wud
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - /home/fcc/whatsupdocker/docker-compose.yml:/wud/wud/docker-compose.yml
      - /home/fcc/paperless-ngx/docker-compose.yml:/wud/paperless-ngx/docker-compose.yml
    ports:
      - 3000:3000
    environment:
      - WUD_AUTH_BASIC_FCC_USER=myusername
      - WUD_AUTH_BASIC_FCC_HASH=mypasswordhash1234
      - WUD_TRIGGER_DOCKERCOMPOSE_WUD_FILE=/wud/wud/docker-compose.yml
      - WUD_TRIGGER_DOCKERCOMPOSE_WUD_BACKUP=true
      - WUD_TRIGGER_DOCKERCOMPOSE_PAPERLESSNGX_FILE=/wud/paperless-ngx/docker-compose.yml
      - WUD_TRIGGER_DOCKERCOMPOSE_PAPERLESSNGX_BACKUP=true

that should have it auto updating, and should make it easy to just use the backup file when it dies

ok you can stop ignoring now

what’s up docker gave me enough issues that i stopped using it. I noticed sudden, unexpected downtime for paperless, and decided it was not worth using.