From 3d27c94595376440e1e467cd0e1bba9568e071c6 Mon Sep 17 00:00:00 2001 From: canepan Date: Mon, 2 May 2022 06:20:30 +0100 Subject: [PATCH 1/2] Update README.md Signed-off-by: Nicola Canepa Mention the required update to docker.io in additon to libseccomp2 on ARM --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index d8ec7bc..9854b78 100644 --- a/README.md +++ b/README.md @@ -13,7 +13,7 @@ The first recommendation is to upgrade your host OS, which will include a more up to date (and fixed) version of `libseccomp`. - _If you absolutely cannot do this, some users [have reported](https://github.com/pi-hole/docker-pi-hole/issues/1042#issuecomment-1086728157) success in updating `libseccomp2` via backports on debian, or similar via updates on Ubuntu. You can try this workaround at your own risk_ + _If you absolutely cannot do this, some users [have reported](https://github.com/pi-hole/docker-pi-hole/issues/1042#issuecomment-1086728157) success in updating `libseccomp2` via backports and `docker.io` from bullseye on debian (more details [here](https://blog.samcater.com/fix-workaround-rpi4-docker-libseccomp2-docker-20/)) on debian, or similar via updates on Ubuntu. You can try this workaround at your own risk_ - Some users [have reported issues](https://github.com/pi-hole/docker-pi-hole/issues/963#issuecomment-1095602502) with using the `--privileged` flag on `2022.04` and above. TL;DR, don't use that that mode, and be [explicit with the permitted caps](https://github.com/pi-hole/docker-pi-hole#note-on-capabilities) (if needed) instead From 0e7013e890fae2a48ffc4e14b2d2d0aeab3f23a2 Mon Sep 17 00:00:00 2001 From: Adam Warner Date: Mon, 23 May 2022 17:15:47 +0100 Subject: [PATCH 2/2] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 9854b78..2f8e9c5 100644 --- a/README.md +++ b/README.md @@ -13,7 +13,7 @@ The first recommendation is to upgrade your host OS, which will include a more up to date (and fixed) version of `libseccomp`. - _If you absolutely cannot do this, some users [have reported](https://github.com/pi-hole/docker-pi-hole/issues/1042#issuecomment-1086728157) success in updating `libseccomp2` via backports and `docker.io` from bullseye on debian (more details [here](https://blog.samcater.com/fix-workaround-rpi4-docker-libseccomp2-docker-20/)) on debian, or similar via updates on Ubuntu. You can try this workaround at your own risk_ + _If you absolutely cannot do this, some users [have reported](https://github.com/pi-hole/docker-pi-hole/issues/1042#issuecomment-1086728157) success in updating `libseccomp2` via backports on debian, or similar via updates on Ubuntu. You can try this workaround at your own risk_ (Note, you may also find that you need the latest `docker.io` (more details [here](https://blog.samcater.com/fix-workaround-rpi4-docker-libseccomp2-docker-20/)) - Some users [have reported issues](https://github.com/pi-hole/docker-pi-hole/issues/963#issuecomment-1095602502) with using the `--privileged` flag on `2022.04` and above. TL;DR, don't use that that mode, and be [explicit with the permitted caps](https://github.com/pi-hole/docker-pi-hole#note-on-capabilities) (if needed) instead