Jerry Koerkenmeier

Funny thing is - I had paperless working great in docker sometime back before I needed to backup & remove "Container Station" and reinstall it (which installs docker and docker-compose...

I created a new container with a different entrypoint and ran all 4 of your other statements: `[/share/Apps/paperless/paperless-master] # docker run -it --entrypoint /bin/sh 78af583de43b -c /bin/sh paperless_webserver_1` `/usr/src/paperless/src #...

I thought about setting the PID=0 and GID=0 but that didn't work because the app complains that the user already exists.

Maybe you can explain how the container creates the paperless user: why is it necessary, why do the chown at all? Can't it just be run as root or whichever...

Doesn't docker run the image as root (uid 0) anyway? Why the need to create a new user and group? My guess is that building the container in the Dockerfile...

There's also a `chown` in the Dockerfile: `chown -Rh paperless:paperless /usr/src/paperless && \` Should that be commented out as well?

@fredericrous Yeah - they don’t understand the problem. This is actually a major bug you’ve discovered and several of us have but failed to document perhaps. I’d use something simple...

Still working on a good logging solution worth publishing. I'm also working on Promtail + Loki + Grafana, but not sure when I'll finish it. I've had problems with cadvisor...

Precisely. Same problem. How do we successfully bind mount to a directory to persist data?

@dtomcej - > Of note, there are 3 sources of http -> https redirects, that exist: > > 1. The redirection middleware on entrypoints > 2. The redirection middleware on...