Use correct namespace for serverstransport

pull/330/head
thespad 2025-07-05 20:22:34 +01:00
rodzic 131b358b2a
commit ae87b24dbf
Nie znaleziono w bazie danych klucza dla tego podpisu
1 zmienionych plików z 16 dodań i 16 usunięć

Wyświetl plik

@ -6,7 +6,7 @@ hide:
??? faq "My host is incompatible with images based on Ubuntu Jammy" ??? faq "My host is incompatible with images based on Ubuntu Jammy"
##### My host is incompatible with images based on Ubuntu Jammy { #jammy } ##### My host is incompatible with images based on Ubuntu Jammy { #jammy }
=== "Description" === "Description"
@ -53,7 +53,7 @@ hide:
??? faq "My host is incompatible with images based on rdesktop" ??? faq "My host is incompatible with images based on rdesktop"
##### My host is incompatible with images based on rdesktop { #rdesktop } ##### My host is incompatible with images based on rdesktop { #rdesktop }
=== "Description" === "Description"
@ -82,7 +82,7 @@ hide:
??? faq "My host is incompatible with images based on Ubuntu Focal and Alpine 3.13 and later" ??? faq "My host is incompatible with images based on Ubuntu Focal and Alpine 3.13 and later"
##### My host is incompatible with images based on Ubuntu Focal and Alpine 3.13 and later { #libseccomp } ##### My host is incompatible with images based on Ubuntu Focal and Alpine 3.13 and later { #libseccomp }
=== "Description" === "Description"
@ -143,7 +143,7 @@ hide:
??? faq "My host filesystem is incompatible with my docker storage driver" ??? faq "My host filesystem is incompatible with my docker storage driver"
##### My host filesystem is incompatible with my docker storage driver { #storage } ##### My host filesystem is incompatible with my docker storage driver { #storage }
=== "Description" === "Description"
@ -172,7 +172,7 @@ hide:
??? faq "What is lscr.io" ??? faq "What is lscr.io"
##### What is lscr.io { #lscr } ##### What is lscr.io { #lscr }
LSCR is a vanity url for our images, this is provided to us in collaboration with [scarf.sh](https://about.scarf.sh/). It is not a dedicated docker registry, rather a redirection service. As of writing it redirects to GitHub Container Registry (ghcr.io). LSCR is a vanity url for our images, this is provided to us in collaboration with [scarf.sh](https://about.scarf.sh/). It is not a dedicated docker registry, rather a redirection service. As of writing it redirects to GitHub Container Registry (ghcr.io).
@ -186,7 +186,7 @@ hide:
??? faq "I cannot connect to lscr.io" ??? faq "I cannot connect to lscr.io"
##### I cannot connect to lscr.io { #lscr-no-connect } ##### I cannot connect to lscr.io { #lscr-no-connect }
Due to the nature of Scarf as a Docker gateway which gathers usage metrics, some overzealous privacy-focused blocklists will include its domains. Due to the nature of Scarf as a Docker gateway which gathers usage metrics, some overzealous privacy-focused blocklists will include its domains.
@ -220,7 +220,7 @@ hide:
??? faq "I want to reverse proxy an application which defaults to https with a self-signed certificate" ??? faq "I want to reverse proxy an application which defaults to https with a self-signed certificate"
##### I want to reverse proxy an application which defaults to https with a self-signed certificate { #strict-proxy } ##### I want to reverse proxy an application which defaults to https with a self-signed certificate { #strict-proxy }
=== "Traefik" === "Traefik"
@ -230,21 +230,21 @@ hide:
```yml ```yml
http: http:
serversTransports: serversTransports:
ignorecert: ignorecert:
insecureSkipVerify: true insecureSkipVerify: true
``` ```
Then on our `foo` service we tell it to use this rule, as well as telling Traefik the backend is running on https. Then on our `foo` service we tell it to use this rule, as well as telling Traefik the backend is running on https.
```yml ```yml
- traefik.http.services.foo.loadbalancer.serverstransport=ignorecert - traefik.http.services.foo.loadbalancer.serverstransport=ignorecert@file
- traefik.http.services.foo.loadbalancer.server.scheme=https - traefik.http.services.foo.loadbalancer.server.scheme=https
``` ```
??? faq "Why does LinuxServer.io recommend to use docker-compose over Portainer?" ??? faq "Why does LinuxServer.io recommend to use docker-compose over Portainer?"
##### Why does LinuxServer.io recommend to use docker-compose over Portainer? { #portainer } ##### Why does LinuxServer.io recommend to use docker-compose over Portainer? { #portainer }
Portainer has many issues which make it hard for us to support, such as: Portainer has many issues which make it hard for us to support, such as:
@ -257,7 +257,7 @@ hide:
??? faq "Inexplicable issues when running ubuntu" ??? faq "Inexplicable issues when running ubuntu"
##### Inexplicable issues when running ubuntu { #snap } ##### Inexplicable issues when running ubuntu { #snap }
=== "Description" === "Description"
@ -309,13 +309,13 @@ hide:
docker: /usr/bin/docker /etc/docker /usr/libexec/docker /snap/bin/docker.machine /snap/bin/docker.help /snap/bin/docker.compose /snap/bin/docker /usr/share/man/man1/docker.1.gz docker: /usr/bin/docker /etc/docker /usr/libexec/docker /snap/bin/docker.machine /snap/bin/docker.help /snap/bin/docker.compose /snap/bin/docker /usr/share/man/man1/docker.1.gz
``` ```
As you can see in the second one, multiple versions can coexist which is a big tshoot problem. As you can see in the second one, multiple versions can coexist which is a big tshoot problem.
Once this is complete, if the expected version isn't present, simply follow [docker install on ubuntu](https://docs.docker.com/engine/install/ubuntu/) Once this is complete, if the expected version isn't present, simply follow [docker install on ubuntu](https://docs.docker.com/engine/install/ubuntu/)
When they finish, running `docker` commands may result in `-bash: /snap/bin/docker: No such file or directory` if this is the case, this is simply a shell patch issue, they can launch a new shell or simply input `hash -r` which should resolve the problem. Version info at the time of this writing should be When they finish, running `docker` commands may result in `-bash: /snap/bin/docker: No such file or directory` if this is the case, this is simply a shell patch issue, they can launch a new shell or simply input `hash -r` which should resolve the problem. Version info at the time of this writing should be
```bash ```bash
~ # docker --version && docker compose version ~ # docker --version && docker compose version
Docker version 24.0.7, build afdd53b Docker version 24.0.7, build afdd53b
Docker Compose version v2.21.0 Docker Compose version v2.21.0
``` ```