-
-
Notifications
You must be signed in to change notification settings - Fork 13
[BUG] Fatal Python Error: pyinit_main: can't initialize time #4
Comments
Thanks for opening your first issue here! Be sure to follow the issue template! |
I second this report. |
This looks like a permissions issue. Ensure that the directory you're mounting for /config and /data are writable by 1000:100 as you've specified. |
Hi Alex - permissions of the directory are fine:
Thanks |
Vorsku what happens if you attempt to run the container without volume mounts (just as a test)? Does it successfully run the migrations then? |
I've tried it without volume mounts and with UID/GID of 1000/1000 and still get the same error. Not sure whether @n00B17 is also using ARM but could be an ARM-specific issue?
|
Ah, I didn't check on ARM. Let me give that a shot. |
yes, I do use arm as well. |
It looks like this bug is related to the focal base image we had to use here. We're still waiting for the ARM issue to be resolved. Once that's resolved upstream, this should no longer be an issue. |
Thanks Alex, I'll keep trying new builds and update this issue when it's resolved. |
same here with rpi 4; any update on this? |
You need a updated version of libseccomp2, 2.4.3-1 or higher. It is currently not available for Raspberry PI OS, but it is for Ubuntu. You can look into downloading the Deb from Ubuntus repository. |
thants @Roxedus will try that! hopefully this can be fixed soon anyways |
Thanks @Roxedus, it looks like that's specific to RPI-OS and Ubuntu Focal. I'll try and fork tomorrow using lsiobase/ubuntu:bionic and see if it works - @alex-phillips would there be any option for a separate papermerge branch built on bionic instead? |
Iirc we had to use focal for a specific reason, so bionic rebase is unlikely to work |
We had to use focal due to package version requirements by papermerge itself that are not available in bionic. |
still cannot make it to work on a rpi 4; neither dev ubuntu version...would love to have this running, can I help somehow? |
What version of |
Im on 2.3.3-4 |
So you did not patch your system to work. It is not a direct problem with the image, but with the
|
I have just tested on Jetson nano, with the back port version of |
The same problem here. Without solution? |
Please let me know when it is functional, please, thank you. |
Hello, I have also faced this issue. I haven't got it working yet on my RPi4 yet, but I'm going to try these solutions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hey guys, any updates for this issue? Still not working for RPi4 .. tried latest build and arm32v7-latest. papermerge_1 | Fatal Python error: pyinit_main: can't initialize time |
For reference, this also affects SWAG under arm32; can confirm the package installation for Buster worked for me. |
Installing libseccomp2_2.5.0-3_armhf.deb on my RPi4 resolved the problem. |
Its Working, thanks!! |
This also solved the problem for me on RPi 4. Thanks! |
Same problem and libseccomp solution works also for a RPi 3 Mod.B V1.2. Thanks |
Also worked with my Raspberry Pi 4 4GB. This is the issue that appeared when doing Step 4/62 : RUN pip3 install --no-cache-dir -r requirements.txt --upgrade pip
---> Running in 3865e8e884e7
Fatal Python error: pyinit_main: can't initialize time
Python runtime state: core initialized
PermissionError: [Errno 1] Operation not permitted
Current thread 0xb6f30010 (most recent call first):
<no Python frame> |
The link above is broken as the package has been updated. this version still fixes the problem.
The link above will probably break in time too. Go to https://packages.debian.org/sid/armhf/libseccomp2/download to find the new version number and put that in the url. Thanks for your help! Had a docker image that was working on another armv7 device but not starting on a pi4. |
Note: you also need Docker >= 19 for this to work, and it can be fixed by using |
If you are new to Docker or this application our issue tracker is ONLY used for reporting bugs or requesting features. Please use our discord server for general support.
Expected Behavior
PaperMerge application should start
Current Behavior
Container starts however PaperMerge doesn't
Steps to Reproduce
Environment
OS: Raspbian
CPU architecture: arm32
How docker service was installed: Raspbian convenience script, all other LSIO images work on the system
Command used to create docker container (run/create/compose/screenshot)
version: "2"
services:
papermerge:
image: linuxserver/papermerge:latest
hostname: papermerge
environment:
- PUID=1000
- PGID=100
- TZ=Europe/London
volumes:
- ${PWD}/config:/config
- ${PWD}/data:/data
ports:
- 8001:8000
Docker logs
Creating network "papermerge_default" with the default driver
Creating papermerge_papermerge_1 ... done
Attaching to papermerge_papermerge_1
papermerge_1 | [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
papermerge_1 | [s6-init] ensuring user provided files have correct perms...exited 0.
papermerge_1 | [fix-attrs.d] applying ownership & permissions fixes...
papermerge_1 | [fix-attrs.d] done.
papermerge_1 | [cont-init.d] executing container initialization scripts...
papermerge_1 | [cont-init.d] 01-envfile: executing...
papermerge_1 | [cont-init.d] 01-envfile: exited 0.
papermerge_1 | [cont-init.d] 10-adduser: executing...
papermerge_1 |
papermerge_1 | -------------------------------------
papermerge_1 | _ ()
papermerge_1 | | | ___ _ __
papermerge_1 | | | / | | | /
papermerge_1 | | | _ \ | | | () |
papermerge_1 | || |/ || __/
papermerge_1 |
papermerge_1 |
papermerge_1 | Brought to you by linuxserver.io
papermerge_1 | -------------------------------------
papermerge_1 |
papermerge_1 | To support LSIO projects visit:
papermerge_1 | https://www.linuxserver.io/donate/
papermerge_1 | -------------------------------------
papermerge_1 | GID/UID
papermerge_1 | -------------------------------------
papermerge_1 |
papermerge_1 | User uid: 1000
papermerge_1 | User gid: 100
papermerge_1 | -------------------------------------
papermerge_1 |
papermerge_1 | [cont-init.d] 10-adduser: exited 0.
papermerge_1 | [cont-init.d] 50-config: executing...
papermerge_1 | Fatal Python error: pyinit_main: can't initialize time
papermerge_1 | Python runtime state: core initialized
papermerge_1 | PermissionError: [Errno 1] Operation not permitted
papermerge_1 |
papermerge_1 | Current thread 0x76efb460 (most recent call first):
papermerge_1 |
papermerge_1 | Fatal Python error: pyinit_main: can't initialize time
papermerge_1 | Python runtime state: core initialized
papermerge_1 | PermissionError: [Errno 1] Operation not permitted
papermerge_1 |
papermerge_1 | Current thread 0x76f13460 (most recent call first):
papermerge_1 |
papermerge_1 | Fatal Python error: pyinit_main: can't initialize time
papermerge_1 | Python runtime state: core initialized
papermerge_1 | PermissionError: [Errno 1] Operation not permitted
papermerge_1 |
papermerge_1 | Current thread 0x76fe3460 (most recent call first):
papermerge_1 |
papermerge_1 | Fatal Python error: pyinit_main: can't initialize time
papermerge_1 | Python runtime state: core initialized
papermerge_1 | PermissionError: [Errno 1] Operation not permitted
papermerge_1 |
papermerge_1 | Current thread 0x76fb6460 (most recent call first):
papermerge_1 |
papermerge_1 | Fatal Python error: pyinit_main: can't initialize time
papermerge_1 | Python runtime state: core initialized
papermerge_1 | PermissionError: [Errno 1] Operation not permitted
papermerge_1 |
papermerge_1 | Current thread 0x76f8d460 (most recent call first):
papermerge_1 |
papermerge_1 | [cont-init.d] 50-config: exited 1.
papermerge_1 | [cont-init.d] 99-custom-scripts: executing...
papermerge_1 | [custom-init] no custom files found exiting...
papermerge_1 | [cont-init.d] 99-custom-scripts: exited 0.
papermerge_1 | [cont-init.d] done.
papermerge_1 | [services.d] starting services
papermerge_1 | [services.d] done.
The text was updated successfully, but these errors were encountered: