[BUG] Webserver not starting after upgrade to 1.4.0 #879
Comments
|
Host OS? Docker version? |
|
Raspberry Pi 4 - Raspbian Buster |
|
Seems I managed to break the ARM image again. |
|
Can we support in any way? |
|
Well, figure out why sudo does not work. I'll do that now. Worst case, I'll revert updating debian dependencies. This release has newer versions of tesseract (from debian testing), and apparently sudo from the same testing repository does not work on ARM (no issues on x86_64 though). Very few google hits. Tricky! :) Firing up the RPi now. |
|
Unable to reproduce this on the RPi, sadly. |
|
I can try to set up a new Docker-compose environment tomorrow to check, if it depends on the update maybe. |
|
Which Pi do you use? |
|
Pi 3B. I don't have a Pi4. Is that on aarch64? |
|
Yes, this is running on aarch64. Maybe, this is the problem? |
|
@starbuck93 - are you running on aarch64? |
|
|
|
Are you both running on Raspbian Buster? |
|
@Bart1909 Yes, it looks like Buster / debian 10 with the 5.10.17 kernel. |
|
I‘m also running on Buster, but with kernel 4.9.118 |
|
Tested it with a fresh paperless-environment on Pi 4 with the same error message. |
|
I have the same issue on RPi4 with Raspbian: |
|
@tobi-bo which Raspbian version do you use? also Buster? |
|
@Bart1909 Yes: |
|
I have the same issue on a fresh install, but with a slightly different error message: I'm also running on a raspberry pi with armv7l and a fresh installation of Buster, on a Pi 3. Using 1.3.2 instead works. |
I am getting the exact same error message since upgrading to 1.4.0. |
Works for me, too. |
|
Pushed a change to the dev branch, please try with the |
|
Tried with the |
|
I first time Installed paperless on a raspberry pi with the script (I assume it would be 1.4). |
|
I'm not familiar with paperless and docker. I installed paperless with the script on my Raspi. |
|
I am still getting the same error with the newest docker release 1.4.1 on a Raspberry Pi 3 Model B: |
|
Same, the latest update broke the webserver. Interestingly, the exit codes alternate |
|
I have this issue too. On 1.4.1.
Standing at the ready for test requests. |
|
Hey @jonaswinkler |
|
I have no idea what's causing this issue and google is not providing any useful insights. The image also works fine on my RPi 3b, which is armhf / 32bit. Probably has something to do with updated binary dependencies in 1.4.0 (tesseract 4.1.0 and others). Some of these updated dependencies were required in order to build the newest versions of some python dependencies on RPi, such as pikepdf. These contain important security fixes, so I can't just roll back these changes. In order to properly fix this issue, I need a debian-based docker base image with at least tesseract 4.1, and python 3.7 (piwheels does not have 3.8 wheels or newer), and support for all three architectures. So far, I was unable to find a well maintained image that fits these criteria. |
|
Is your Pi running on Raspbian Buster @jonaswinkler ? |
|
Yes. |
|
I searched in internet about a solution. I found the propose to add If I do that I get. I get the same Error if I do docker-compose with sudo. Raspberry Pi uname -a ⇒ |
|
That's because the entrypoint script has to be run as root to set up permissions. |
|
I think we are affected by this issue: In the process of debugging it i stumbled upon gosu which is used by postgresql in their docker image and from the description of the debian package it is a lot easier to configure and use if you just want to run as a different user without further issues. |
|
This seems to work @WhiteHatTux ! @jonaswinkler maybe you can add this hint to the documentation for new users? |
I tried suggested Option 3 in that FAQ, and it's working for me. Running on 1.4.1 now, without any issues. Thanks @WhiteHatTux |
|
Just queued 1.4.2, please report back if this works for you. The build takes about an hour. |
|
I tested 1.4.2 and got the following error now (I didn't perform the package update described in #879 (comment) yet): Edit: I performed the package update linked by @WhiteHatTux now and 1.4.2 works as expected. |
|
@jonaswinkler I think I might not have been specific enough in my previous comment/the PR. |
|
I tried with python:3.7-slim-stretch, as the problem is not supposed to affect older versions, but it doesn't work either. |
|
No worries. I've updated libseccomp2 in the docker image. Please report back if the |
|
I will give it a try, but I'm almost certain that it won't work, as the different sources state that the new libseccomp needs to be installed on the host and not inside the image. |
|
Tested 1.4.2, unfortunately I don't manage to get to the point I can test it. docker-compose up makes the webserver service do this: Reverted to 1.3.2 |
|
@sitarane Which language did you set in PAPERLESS_OCR_LANGUAGES environment variable? How are you running paperless? docker-library/php#898 (comment) suggests that it might also be due to the space that was assigned to docker. Depending on the installation method of docker. Edit |
@jonaswinkler I tried the image for 1.4.2 and it doesn't work. Really the only thing I have found to work is the installation of the new libseccomp on the host. :-( |
|
This appears to be bugging quite some people: |
I totally did not get that and reacted too quickly with 1.4.2. Oh well. |
|
I was waiting on the update to have a testable environment. I'll update if we throw the towel in. Are we at that point yet? |
|
@sitarane With all the research I have done on the issue I was not able to find a different solution. It is fairly easy to go back to the previous libseccomp on the host and reproduce the error. I have done the back and forth a few time successfully. I would suggest you upgrade to the new libseccomp, as I don't see any way of this getting fixed otherwise. |
|
Hi i found this |
|
@Radioaktivman thank you very much, this worked flawlessly for me! |
After updating to 1.4.0 the web server will not start.
Docker-Output is:
The text was updated successfully, but these errors were encountered: