darias

Not entirely sure on this one. Did you try homebox:0.23.0?

Bingo. When you browse the /data directory through the Docker console, you're actually looking at files in appdata/homebox on your server. If you didn't have a directory mapping in your Docker configuration to map /data to appdata/homebox, then Homebox is just going to write to the /data directory as usual, which is going to be in the Docker image. Does that make sense?

FWIW, I just went into Homebox and added a location, and the homebox.db file in my appdata/homebox folder updated. Forgive me if you know this already, but the files will appear in the container if you access it via the console. Same files in appdata/homebox on the server, and /data in the container.

This app was failing to start for me from a fresh install with this error in the logs: panic: parsing config: parsing config: conf: error assigning to field ReadTimeout: converting '10' to type time.Duration. details: time: missing unit in duration "10" Updating these environment variables to include an 's' after the numeric value for each resolved the issue: HBOX_WEB_READ_TIMEOUT HBOX_WEB_WRITE_TIMEOUT HBOX_WEB_IDLE_TIMEOUT

My guess is something wrong with the latest update of this Docker (7 days ago). I reverted back to the last update (2 months ago) and it's working again. If you want to try this, edit the Docker and change the repository to be: linuxserver/dokuwiki:2018-04-22c-ls41 No warranties, expressed or implied!