mirror
/
docker-documentation
kopia lustrzana https://github.com/linuxserver/docker-documentation
1
0
Forkuj 0
Kod Zgłoszenia Packages Projekty Wydania Wiki Aktywność

Clarifications

pull/125/head
Roxedus 2023-06-26 16:42:29 +02:00 zatwierdzone przez GitHub
rodzic 6d5655f711
commit c57cfe1f74
Nie znaleziono w bazie danych klucza dla tego podpisu
ID klucza GPG: 4AEE18F83AFDEB23
1 zmienionych plików z 4 dodań i 2 usunięć
Pokaż statystyki Ściągnij plik aktualizacji Ściągnij plik porównania Expand all files Collapse all files

6
FAQ.md
Wyświetl plik

@ -143,9 +143,11 @@ We have some blogpost related to how we utilize Scarf:
### I cannot connect to lscr.io {#lscr-no-connect} ### 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: If Scarf is on the blocklist, you will get a error message like this when trying to pull a image: