Closed offbyone closed 3 years ago
Thanks for opening your first issue here! Be sure to follow the issue template!
We can't. We would not use focal unless we have to. For plex and jellyfin, using bionic would just not let you use certain features.
What version of libseccomp2 do you actually have?
Package: libseccomp2
Version: 2.3.3-4
Priority: optional
Section: libs
Source: libseccomp
Maintainer: Kees Cook <kees@debian.org>
Installed-Size: 161 kB
Depends: libc6 (>= 2.4)
Homepage: https://github.com/seccomp/libseccomp
Download-Size: 33.1 kB
APT-Manual-Installed: yes
APT-Sources: http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
Description: high level interface to Linux seccomp filter
This library provides a high level interface to constructing, analyzing
and installing seccomp filters via a BPF passed to the Linux Kernel's
prctl() syscall.
(I'm gonna be at work today, so I can follow up with troubleshooting late tonight)
You have to do one of the approaches in the wiki, to get a up-to-date package
Sounds good, thanks!
I'm having the same issue. Can you link to the wiki please.
edit: sorry, I believe its the link in the original issue.
edit2: can you explain how you resolved this. I added the repos and installed buster-backports and libseccomp2 but I'm still having the same issue.
Same here I tried with both libseccomp2_2.4.4-1~bpo10+1_armhf and libseccomp2_2.5.0-3_armhf, rebooted but still did not work.
2.5 does not have the patch, 2.5.1 might.
@allenbina @grota What OS' are you guys using?
While responding to this, I restarted the container to get a clean set of logs and it worked. I'm not sure what I did to fix it, but I believe that those two packages might have fixed it, and I needed to restart or something.
To install, I used the docker-cli run command:
docker run -d \
--name=radarr \
-e PUID=1000 \
-e PGID=1000 \
-e TZ=Europe/London \
-e UMASK_SET=022 `#optional` \
-p 7878:7878 \
-v /path/to/data:/config \
-v /path/to/movies:/movies \
-v /path/to/downloadclient-downloads:/downloads \
--restart unless-stopped \
ghcr.io/linuxserver/radarr
I am running raspian buster
$cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
docker 19.03.14
$docker version
Client: Docker Engine - Community
Version: 19.03.14
API version: 1.40
Go version: go1.13.15
Git commit: 5eb3275d40
Built: Tue Dec 1 19:21:06 2020
OS/Arch: linux/arm
Experimental: false
Server: Docker Engine - Community
Engine:
Version: 19.03.14
API version: 1.40 (minimum version 1.12)
Go version: go1.13.15
Git commit: 5eb3275d40
Built: Tue Dec 1 19:19:00 2020
OS/Arch: linux/arm
Experimental: false
containerd:
Version: 1.3.9
GitCommit: ea765aba0d05254012b0b9e595e995c09186427f
runc:
Version: 1.0.0-rc10
GitCommit: dc9208a3303feef5b3839f4323d9beb36df0a9dd
docker-init:
Version: 0.18.0
GitCommit: fec3683
Guys same problem here.
When I enter inside the container and try to run Radarr manually using /app/radarr/bin/Radarr
I get this error: Aborted (core dumped)
.
@afonsof do the fix?
As "doing a bionic tag" on Radarr isn't tractable according to the devs, and since my issue is solved by their existing instructions, as well, I'm closing this. Thanks, team, I appreciate the help!
These troubleshooting page had worked: https://docs.linuxserver.io/faq#my-host-is-incompatible-with-images-based-on-ubuntu-focal
sorry guys for the late reply, I'm leaving here a workaround, since installing the suggested updated libseccomp2 package did not solve the issue for me.
I am also on Raspbian GNU/Linux 10 (buster)
but with an earlier docker version:
Client:
Version: 18.09.1
API version: 1.39
Go version: go1.11.6
Git commit: 4c52b90
Built: Fri, 13 Sep 2019 10:45:43 +0100
OS/Arch: linux/arm
Experimental: false
Server:
Engine:
Version: 18.09.1
API version: 1.39 (minimum version 1.12)
Go version: go1.11.6
Git commit: 4c52b90
Built: Fri Sep 13 09:45:43 2019
OS/Arch: linux/arm
Experimental: false
The workaround for me was to use an older image tag: linuxserver/radarr:arm32v7-version-v0.2.0.1504
I am also on Raspbian GNU/Linux 10 (buster) but with an earlier docker version:
Then update your docker?
Radarr v3 does not work on the bionic baseimage, you'll have to fix your host environment.
for some odd reason (that right now I don't want to investigate) even after an apt update I only see 18.09.1+dfsg1-7.1+rpi1+rpt1
18.09.1+dfsg1-7.1+rpi1+deb10u2
as versions available for the docker.io package. Thanks for the info about v3, debugging and resolving the upgrade issue is an issue for future me :)
We recommend installing docker from the official repos: https://docs.docker.com/engine/install/debian/ Alternatively, you can try the convenient get docker script: https://get.docker.com/
Expected Behavior
radarr should start on my Raspberry Pi
Current Behavior
It does not :)
Looking at https://docs.linuxserver.io/faq#my-host-is-incompatible-with-images-based-on-ubuntu-focal I see that I am getting the same date symptom as described there:
My pi has this architecture:
The service doesn't appear to be running inside the container:
Environment
OS: Raspbian CPU architecture: armv7l How docker service was installed: Via the geerlingguy ansible role
Command used to create docker container (run/create/compose/screenshot)
Via compose file:
Docker logs