cannot install: s6-svscan: warning: unable to iopause: Operation not permitted

[slinky07]

Describe the bug
cannot successfully install

To Reproduce
Steps to reproduce the behavior:
use the following docker compose

version: '3.3'
services:
▏ ▏ speedtest-tracker:
▏ ▏ ▏ ▏ container_name: speedtest-tracker
▏ ▏ ▏ ▏ ports:
▏ ▏ ▏ ▏ ▏ ▏ - '80:80'
▏ ▏ ▏ ▏ ▏ ▏ - '8443:443'
▏ ▏ ▏ ▏ environment:
▏ ▏ ▏ ▏ ▏ ▏ - PUID=1000
▏ ▏ ▏ ▏ ▏ ▏ - PGID=1000
▏ ▏ ▏ ▏ volumes:
▏ ▏ ▏ ▏ ▏ ▏ - './speedtest-tracker:/config'
▏ ▏ ▏ ▏ image: 'ghcr.io/alexjustesen/speedtest-tracker:latest'
▏ ▏ ▏ ▏ restart: unless-stopped

used 80 cause 8080 already binded
Expected behavior
having app running. I don't understand what's up with s6-svscan error.

Environment (please complete the following information):

• OS: raspberry pi 4b
• Architecture: armv7l
• Browser safari
• Version latest

Screenshots
If applicable, add screenshots to help explain your problem.

Logs
_speedtest-tracker_logs-2.txt

Additional context
is searched the error online and stuff but I don't understand what im doing wrong. I tried with different ports and it's not fixing it. thanks a lot for any assistance.
I should note, on my Mac m1, I am able to successfully run it with same docker compose except that ports is on 8080 instead of 80.

[alexjustesen]

Well that's a new one... I'll look into it this week. Take a look at this from PiHole, they mention issues with older version of Docker Engine and Ubuntu 22.04, what is your DE version?

[alexdelprete]

Could it be a permission error due to the PID=1000 /PGID=1000 used in the docker-compose? Does 1000/1000 actually exist at OS level? Does it have the right permissions? I don't know...just speculating...:)

[slinky07]

I am on Raspberry Pi OS with the following docker engine version

Client: Docker Engine - Community
 Version:           20.10.22
 API version:       1.41
 Go version:        go1.18.9
 Git commit:        3a2c30b
 Built:             Thu Dec 15 22:27:56 2022
 OS/Arch:           linux/arm
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.22
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.18.9
  Git commit:       42c8b31
  Built:            Thu Dec 15 22:25:44 2022
  OS/Arch:          linux/arm
  Experimental:     false
 containerd:
  Version:          1.6.15
  GitCommit:        5b842e528e99d4d4c1686467debf2bd4b88ecd86
 runc:
  Version:          1.1.4
  GitCommit:        v1.1.4-0-g5fd4c4d
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

       #######          --------------
       ##O#O##          OS: Linux (Unknown) armv7l
       #######          Host: Raspberry Pi 4 Model B Rev 1.4
     ###########        Kernel: 5.15.68-v7l+
    #############       Uptime: 11 days, 3 hours, 18 mins
   ###############      Packages: 1944 (dpkg), 2 (snap)
   ################     Shell: bash 5.0.3
  #################     Resolution: 1920x1080
#####################   Terminal: /dev/pts/0
#####################   CPU: BCM2711 (4) @ 1.500GHz
  #################     Memory: 1262MiB / 7898MiB

am not certain if the PID=1000 /PGID=1000 comment is right tr not tbh, I used the compose from the documentation with - PUID=1000 - PGID=1000 , unless it can be a issue with my pi on pi os? the pi hole link mentioned raspbian buster and a few of the Debian ...

[alexjustesen]

Try running id usernamehere so if your default user on your Pi is root you can do id root and it will tell you what your PDIG and PUID are.

[alexdelprete]

am not certain if the PID=1000 /PGID=1000 comment is right tr not tbh

Make sure to use a userid/groupid of a user that has access to the ./speedtest-tracker folder you used in the volume mapping.

PID/PGID are used for this:

(source)

[slinky07]

thanks, will try all that after work or in the morning!

[slinky07]

my uid and gid are as following
when I run id $user I get :
uid=1000(pi) gid=1000(pi)
seems like that should be fine? Im under ssh tunnel so might be a bit difficult to change my uid, from my understanding.
let me know if that could be the issue

[alexjustesen]

@slinky07 is docker running as the root user on your machine or as another?

[slinky07]

yeah it is running as root. I even did sudo user mod -aG docker pi but that didn't do anything.

but I was able to fix it! was a headache but the problem is libseccomp, on pi some people have issues with it.

I tried to upgrade it to 2.5.4-1 as homebridge/docker-homebridge#434 (comment) suggests, but that didn't work and I had depedency issues as I have the 2.3.3-4 version

dpkg: dependency problems prevent configuration of libseccomp-dev:armhf:
 libseccomp-dev:armhf depends on libseccomp2 (= 2.5.4-1+b2); however:
  Version of libseccomp2:armhf on system is 2.3.3-4.

there's a few other things I tried from that thread, like homebridge/docker-homebridge#434 (comment) which didn't work too

only homebridge/docker-homebridge#434 (comment) worked, which seems like a temporary solution/workaround, but it works.
I guess I just gotta find how to manually upgrade libseccomp.

altho the last comment on that thread seems promising I might try it homebridge/docker-homebridge#434 (comment)
putting links in case someone else has that issue here.

[alexdelprete]

@slinky07 did you try also this? homebridge/docker-homebridge#434 (comment)

This also looks good: homebridge/docker-homebridge#434 (comment)

[slinky07]

thanks, will check those out too!