bgunson/onboardpi

OAP16 libseccomp2 patch

Opened this issue · 3 comments

OAP 16 comes with an out-of-date version of libseccomp which causes issues with Docker/Docker compose and prevents the database container from starting up. To fix this, run:

wget http://ftp.us.debian.org/debian/pool/main/libs/libseccomp/libseccomp2_2.5.4-1+b3_armhf.deb
sudo dpkg -i libseccomp2_2.5.4-1+b3_armhf.deb

On your raspberry pi and retry running the docker compose commands.

Link to libseccomp2 download (ARM): https://packages.debian.org/sid/armhf/libseccomp2/download

The above fix use the bullseye (Debian 11) version of libseccomp2. Can also try the buster-backport version if 2.5.4-1+b3 does not work.

wget http://ftp.us.debian.org/debian/pool/main/libs/libseccomp/libseccomp2_2.5.1-1~bpo10+1_armhf.deb
sudo dpkg -i libseccomp2_2.5.1-1~bpo10+1_armhf.deb

Hi bgunson, first of all well done for this project.

I trying to deploy it on my setup but the db container is continually restarting due to the below error:

2024-04-04 15:24:02.116 GMT [1] LOG: starting PostgreSQL 14.11 on arm-unknown-linux-musleabihf, compiled by gcc (Alpine 12.2.1_git20220924-r10) 12.2.1 20220924, 32-bit
2024-04-04 15:24:02.116 GMT [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
2024-04-04 15:24:02.116 GMT [1] LOG: listening on IPv6 address "::", port 5432
2024-04-04 15:24:02.121 GMT [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2024-04-04 15:24:02.923 GMT [23] FATAL: the database system is starting up
2024-04-04 15:24:03.670 GMT [1] LOG: startup process (PID 22) was terminated by signal 11: Segmentation fault
2024-04-04 15:24:03.670 GMT [1] LOG: aborting startup due to startup process failure
2024-04-04 15:24:03.762 GMT [1] LOG: database system is shut down

I have also downloaded the above libseccomp2 but this issue persisted. Any Idea what is causing this?

Thanks
Eman

Hi @emancicca, I will investigate this and get back to you. Are you using OpenAuto Pro? Can you please send me your kernel version by running uname -r as well as lsb_release -a? Thanks