Describe the bug
Upon running papra through docker, it errors out and exits with:
papra | ELIFECYCLE Command failed with exit code 132.
papra | ELIFECYCLE Command failed with exit code 132.
What happened?
I used the docker compose files and other commands given in the docker-compose.yml generator. Initially it threw some permission error with sqlite being unable to open a db files, but that was fixed with chmod 777 -R *. Then I started running into the bug as described above. My docker compose is as follows:
services:
papra:
image: ghcr.io/papra-hq/papra:latest
container_name: papra
restart: unless-stopped
ports:
- 1221:1221
environment:
- AUTH_SECRET=<Secret>
- APP_BASE_URL=http://localhost:1221
volumes:
- ./app-data:/app/app-data
user: 1000:1000and the directory permissions and user IDs are as follows:
$ ls -al
drwxrwxrwx 4 user user 33 Apr 10 13:08 app-data
-rwxrwxrwx 1 user user 338 Apr 10 13:23 compose.yaml
-rw-rw-r-- 1 user user 96 Apr 10 03:19 .env
$ id -u && id -g
1000
1000
I've additionally tried the root image and modified the docker compose file as such, but it did not work either. They all result in the same output:
$ docker compose up
[+] up 2/2
✔ Network papra_default Created 0.1s
✔ Container papra Created 0.1s
Attaching to papra
papra |
papra | > @papra/app-server@0.0.0 start:with-migrations /app
papra | > pnpm migrate:up:prod && pnpm start
papra |
papra |
papra | > @papra/app-server@0.0.0 migrate:up:prod /app
papra | > tsx src/scripts/migrate-up.script.ts
papra |
papra | ELIFECYCLE Command failed with exit code 132.
papra | ELIFECYCLE Command failed with exit code 132.
papra exited with code 132 (restarting)
What I expected was for it to not give me an error on ELIFECYCLE or some permission error.
System information
$ docker info
Client: Docker Engine - Community
Version: 29.3.1
Context: rootless
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.33.0
Path: /usr/libexec/docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v5.1.1
Path: /usr/libexec/docker/cli-plugins/docker-compose
Server:
Containers: x
Running: x
Paused: x
Stopped: x
Images: x
Server Version: 29.3.1
Storage Driver: overlayfs
driver-type: io.containerd.snapshotter.v1
Logging Driver: json-file
Cgroup Driver: systemd
Cgroup Version: 2
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
CDI spec directories:
/etc/cdi
/var/run/cdi
/home/carrot/.config/cdi
/run/user/1000/cdi
Swarm: inactive
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 301b2dac98f15c27117da5c8af12118a041a31d9
runc version: v1.3.4-0-gd6d73eb8
init version: de40ad0
Security Options:
seccomp
Profile: builtin
rootless
cgroupns
Kernel Version: 6.12.57+deb13-amd64
Operating System: Debian GNU/Linux 13 (trixie)
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 1.917GiB
Name: <secret>
ID: <secret>
Docker Root Dir: /home/user/.local/share/docker
Debug Mode: false
Experimental: false
Insecure Registries:
127.0.0.0/8
::1/128
Live Restore Enabled: false
Firewall Backend: iptables
WARNING: No cpuset support
WARNING: No io.weight support
WARNING: No io.weight (per device) support
WARNING: No io.max (rbps) support
WARNING: No io.max (wbps) support
WARNING: No io.max (riops) support
WARNING: No io.max (wiops) supportWhere did you encounter the bug?
A self hosted instance
Describe the bug
Upon running papra through docker, it errors out and exits with:
What happened?
I used the docker compose files and other commands given in the docker-compose.yml generator. Initially it threw some permission error with sqlite being unable to open a db files, but that was fixed with
chmod 777 -R *. Then I started running into the bug as described above. My docker compose is as follows:and the directory permissions and user IDs are as follows:
$ ls -al drwxrwxrwx 4 user user 33 Apr 10 13:08 app-data -rwxrwxrwx 1 user user 338 Apr 10 13:23 compose.yaml -rw-rw-r-- 1 user user 96 Apr 10 03:19 .env $ id -u && id -g 1000 1000I've additionally tried the root image and modified the docker compose file as such, but it did not work either. They all result in the same output:
What I expected was for it to not give me an error on ELIFECYCLE or some permission error.
System information
Where did you encounter the bug?
A self hosted instance