Assert failed /build/sync/util/posix/util_posix.cpp:164

RobertSasak commented 2 years ago

Expected Behavior

Resilio shows web UI.

Current Behavior

Resilio does not start. Web UI is not opening.

Steps to Reproduce

$ docker stop resilio-sync && docker rm resilio-sync
$ docker run -d \
  --name=resilio-sync \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Europe/Brussel \
  -p 8888:8888 \
  -p 55555:55555 \
  -v /home/pi/rsync2/config:/config \
  -v /home/pi/rsync2/downloads:/downloads \
  -v /home/pi/rsync2/sync:/sync \
  linuxserver/resilio-sync

However when I try to run a different older tag resilio starts as expected. This tag works.

$ docker run -d \
  --name=resilio-sync \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Europe/Brussel \
  -p 8888:8888 \
  -p 55555:55555 \
  -v /home/pi/rsync2/config:/config \
  -v /home/pi/rsync2/downloads:/downloads \
  -v /home/pi/rsync2/sync:/sync \
  linuxserver/resilio-sync:2.7.2.1375-ls60

My guess it that latest tag is somehow pointing to wrong version/plarform.

$ docker images linuxserver/resilio-sync
REPOSITORY                 TAG                 IMAGE ID       CREATED         SIZE
linuxserver/resilio-sync   latest              d0c09ee42c83   2 weeks ago     147MB  <-- Does not work
linuxserver/resilio-sync   2.7.2.1375-1-ls96   ebb05411d6b3   4 weeks ago     147MB  <--Does not work
linuxserver/resilio-sync   2.7.2.1375-ls60     b691ba475c16   15 months ago   99.7MB <-- Works
linuxserver/resilio-sync   2.7.1.1370-ls59     2525504cea55   15 months ago   99.8MB <-- Works

Environment

OS: Raspbian GNU/Linux 10 (buster) CPU architecture: arm32 (arm/v7) How docker service was installed: don't know

docker --version
Docker version 20.10.9, build c2ea9bc

Command used to create docker container (run/create/compose/screenshot)

Docker logs

$ docker logs resilio-sync > latest.txt

[timestamp error 1 Operation not permitted] assert failed /build/sync/util/posix/util_posix.cpp:164
[timestamp error 1 Operation not permitted] assert failed /build/sync/util/posix/util_posix.cpp:164
[timestamp error 1 Operation not permitted] assert failed /build/sync/util/posix/util_posix.cpp:164
[timestamp error 1 Operation not permitted] assert failed /build/sync/util/posix/util_posix.cpp:164
...
(several pages of the same message)

Above error is outputed to terminal but it does not show up in the actual log. Here is an actual log.

$ cat latest.txt

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 01-envfile: executing... 
[cont-init.d] 01-envfile: exited 0.
[cont-init.d] 10-adduser: executing... 
-------------------------------------
          _         ()
         | |  ___   _    __
         | | / __| | |  /  \
         | | \__ \ | | | () |
         |_| |___/ |_|  \__/
Brought to you by linuxserver.io
-------------------------------------
To support LSIO projects visit:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------
User uid:    1000
User gid:    1000
-------------------------------------
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Your DockerHost is most likely running an outdated version of libseccomp
To fix this, please visit https://docs.linuxserver.io/faq#libseccomp
Some apps might not behave correctly without this
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-config: executing... 
[cont-init.d] 30-config: exited 0.
[cont-init.d] 90-custom-folders: executing... 
[cont-init.d] 90-custom-folders: exited 0.
[cont-init.d] 99-custom-scripts: executing... 
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-scripts: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.

github-actions[bot] commented 2 years ago

Thanks for opening your first issue here! Be sure to follow the bug or feature issue templates!

aptalca commented 2 years ago

Your docker log tells you what the issue is

RobertSasak commented 2 years ago

I see. Thank you. That was the solution. For future reference the solution is to install libseccomp2 >= 2.4.1. The easiest way is the following.

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

For more information about this issue please visit https://docs.linuxserver.io/faq#libseccomp

linuxserver / docker-resilio-sync