Closed jkms closed 1 year ago
I'm trying to deploy the docker container on a Raspberry Pi 3 with an Anker PowerConf S330 connected, but I'm getting the same error as above. My docker-compose is also the same, except for the --debug
at the end.
EDIT: after some googling, this error may be due to an outdated version of libseccomp2. I am indeed running an older version of Raspbian. I'm going to try the solutions proposed here: FAQ - LinuxServer.io
EDIT2: I now have the container running after applying option 2 from the link above. I did have to add an extra command between the second and third line: sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 6ED0E7B82643E131
The docker image contains an error: #33 . The issue was fixed but the fix did not make in into the latest docker image, yet. You have to wait until a new image was built and pushed or just build a new image from the Dockerfile.
Confirming that @seppeel's solution worked. I'm also on a old version (Raspbian GNU/Linux 10 (buster)
) and the following fixed the error above:
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 04EE7237B7D453EC 648ACFD622F3D138
echo "deb http://deb.debian.org/debian buster-backports main" | sudo tee -a /etc/apt/sources.list.d/buster-backports.list
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 6ED0E7B82643E131
sudo apt update
sudo apt install -t buster-backports libseccomp2
I am trying to deploy this on a Pi 3 using the Google AIY voice hat. I installed a fresh image, updated, installed docker and tried to start the container I used this config:
and see this error in the logs:
Unsure where to go from here.