Running container in elevated mode

PabloScolpino commented 3 years ago

To avoid this initialisation failure on a raspberry PI 4 8gb model (Linux raspberrypi 5.10.17-v7l+ #1421 SMP Thu May 27 14:00:13 BST 2021 armv7l GNU/Linux).

speedtest_1   | Current thread 0xb6fa0390 (most recent call first):
speedtest_1   | <no Python frame>
speedtest_1   | Fatal Python error: init_interp_main: can't initialize time
speedtest_1   | Python runtime state: core initialized
speedtest_1   | PermissionError: [Errno 1] Operation not permitted

Also fixed the speedtest container version, in case the maintainer does some weird breaking change in the future.

MiguelNdeCarvalho commented 3 years ago

Hey guys,

First of all this is all related to libseccomp2 on Raspberry Pi OS 32bit (Debian). There was an issue related to that in my repo https://github.com/MiguelNdeCarvalho/speedtest-exporter/issues/71#issuecomment-846424938 . In my opinion there is no need to run the image with tty, stdin_open neither with privileged.

Thanks, MiguelNdeCarvalho

geerlingguy commented 3 years ago

@MiguelNdeCarvalho is correct, and I believe that the problem is resolved by updating libseccomp2 as he mentioned (and see the fix in my internet-pi repository here: https://github.com/geerlingguy/internet-monitoring/issues/17

Note that this should only affect those running on the 32-bit versions of Pi OS.

geerlingguy / internet-monitoring

Running container in elevated mode #16