From f6485e8312fcc9c9a4546d3a26c7ad1b18d48b40 Mon Sep 17 00:00:00 2001 From: Roxedus Date: Mon, 26 Jun 2023 16:42:29 +0200 Subject: [PATCH] Clarifications --- FAQ.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/FAQ.md b/FAQ.md index 8757d3e3da..5545496918 100644 --- a/FAQ.md +++ b/FAQ.md @@ -143,9 +143,11 @@ We have some blogpost related to how we utilize Scarf: ### I cannot connect to lscr.io {#lscr-no-connect} -Due to the nature of Scarf, it sometimes happen to get into larger blocklists focusing on privacy. +Due to the nature of Scarf as a Docker gateway which gathers usage metrics, some overzealous privacy-focused blocklists will include its domains. -If you still want to help us getting a better overview of over containers, you should add `gateway.scarf.sh` to the allowlist in your blocklist solution. +If you want to help us in getting a better overview of how people use our containers, you should add `gateway.scarf.sh` to the allowlist in your blocklist solution. + +Alternatively, you can use Docker Hub or GHCR directly to pull your images, although be aware that all public registries gather user metrics, so this doesn't provide you with any real benefit in that area. If Scarf is on the blocklist, you will get a error message like this when trying to pull a image: