mirror of
https://github.com/ciur/papermerge.git
synced 2026-04-25 03:55:58 +03:00
[GH-ISSUE #295] docker-compose fails with "invalid signature" on raspberry #239
Labels
No labels
2.1
3.0
3.0.1
3.0.2
3.0.3
3.0.3
3.1
3.2
3.2
3.3
3.5
3.x
Fixed. Waiting for feedback.
Fixed. Waiting for feedback.
UX
Version 2.1 - alpha
XSS
announcement
beta
blocker
bug
cannot reproduce
confirmed
confirmed
critical
demo
dependencies
deployment
detchnical debt
discussion
docker
documentation
donations
duplicate
enhancement
feature request
frontend
fundraising
good first issue
good issue
help wanted
high
implemented
important
improvement
incomplete
invalid
investigation
kubernetes
low
low impact
medium
medium
medium impact
migration from 2.0
migration from 2.1
missing-language
missing-ocr-language
no-activity
note
ocr
outofscope
packaging
performance
popular request
pull-request
pypi
question
raspberry pi
roadmap
search
security
setup
status
task
technical debt
updates
user xp
version 1.4.0 - demo
will be implemented
will not be implemented
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/papermerge#239
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @luebbe on GitHub (Feb 3, 2021).
Original GitHub issue: https://github.com/ciur/papermerge/issues/295
Originally assigned to: @ciur on GitHub.
First of all I think the three line build instructions need a little update. At least for me on a raspberry 3b they were:
docker-compose upin docker/1.4 results in the following output:When I run
docker-compose upin docker/1.2 it "finishes", but fails with the error:So in 1.2 the compose finishes, but service and worker fail to start.
@ciur commented on GitHub (Feb 7, 2021):
Hi @luebbe,
I don't own a Raspberry Pi and I personally never intended to run Papermerge on that platform. However, I know many people do that and maybe someone who runs Papermerge on Raspberry Pi can can help you here.
This is definitely not a bug.
@luebbe commented on GitHub (Feb 7, 2021):
Thanks for the feedback. Will investigate further. It definitely wasn't a feature request, so I started with the "bug" template :D
Any idea why the 1.2 version fails to start the services?
@luebbe commented on GitHub (Feb 7, 2021):
OK, I found the following article:
https://askubuntu.com/questions/1263284/apt-update-throws-signature-error-in-ubuntu-20-04-container-on-arm
and intstalled the current version of
libseccompmanually. Now docker-compose builds in 1.4.If this is everything needed to get up and running on a Raspberry, maybe add a line to the docs?
I'll keep you updated.
@luebbe commented on GitHub (Feb 7, 2021):
Making progress. Now step 26/29 fails
I tried again after installing the two dev packages with
sudo apt install libxml2-dev libxslt-dev python-devon the host, but got the same error.I'm a total docker noob, but I guess the dev packages should be installed in the container? No idea how to achieve this.
@amo13 commented on GitHub (Feb 7, 2021):
I never used docker. Maybe you can deploy papermerge more easily if you use ArchLinuxArm and the package I created for archlinux.
If docker just spins up an OS image and runs a script, you might be able to script the installation easily.
Just an idea.
@luebbe commented on GitHub (Feb 8, 2021):
@amo13 sorry, not going to reinstall the system from scratch for a package that I want to try out. I'm glad that I got out of the python version hell by running Home Assistant in a docker container.
@amo13 commented on GitHub (Feb 8, 2021):
Of course! But you might be able to use an archlinux docker image and run the installation of papermerge on the archlinux inside the docker container? Or maybe I just have a misconception of how docker works...
@luebbe commented on GitHub (Feb 8, 2021):
Made a little more progress by adding four -dev packages to the apt-get update section in app.dockerfile:
docker-compose up gets a lot further, but still fails in 26/29:
Looks like I have to install the Rust compiler, but my google fu hasn't helped me to solve this (yet).
@ciur commented on GitHub (Feb 9, 2021):
@luebbe, docker is not the magic pill; docker itself is nothing more than piece of software with its own dependency issues and problems. :) In case you cannot run Papermerge via docker, I suggest to try manual installation. Manual installation is very well documented (well, for Ubuntu 20) and you shouldn't encounter any issue (unless some binaries incompatibilities of your platform). At very least, if you encounter a problem with manual installation it will be simpler to troubleshoot the problem.
@luebbe commented on GitHub (Feb 9, 2021):
Yes, I know :) It's all software...
I had a very good experience moving my HA installation from manual (virtualenv) to docker. It was no joy having to update python whenever HA required a recent version and raspbian was still a few versions behind.
So I went for docker straight away, hoping to avoid these kind of problems. I was also hoping that I could slowly dig myself through the docker installation and get it up and running in order to provide help for others who want to go the same path.
I'll think this through and see how I'll continue.