kopia lustrzana https://github.com/linuxserver/docker-documentation
quietsy
GitHub
rodzic
63ee12ac5b
commit
9aa0a41bc3
94
docs/FAQ.md
94
docs/FAQ.md
|
|
@ -1,12 +1,18 @@
|
|||
# FAQ
|
||||
---
|
||||
hide:
|
||||
- navigation
|
||||
---
|
||||
# Frequently Asked Questions
|
||||
|
||||
Here resides some Frequently Asked Questions.
|
||||
??? 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"
|
||||
|
||||
Some x86_64 hosts running older versions of the Docker engine are not compatible with some images based on Ubuntu Jammy.
|
||||
|
||||
### Symptoms
|
||||
=== "Symptoms"
|
||||
|
||||
If your host is affected you may see errors in your containers such as:
|
||||
|
||||
|
|
@ -26,13 +32,13 @@ Or
|
|||
WARNING :: MAIN : webStart.py:initialize:249 : can't start new thread
|
||||
```
|
||||
|
||||
### Resolution
|
||||
=== "Resolution"
|
||||
|
||||
#### Long-Term Fix
|
||||
<h4>Long-Term Fix</h4>
|
||||
|
||||
Upgrade your Docker engine to at least version `20.10.10`. [Refer to the official Docker docs for installation/update details.](https://docs.docker.com/engine/install)
|
||||
|
||||
#### Short-Term Fix
|
||||
<h4>Short-Term Fix</h4>
|
||||
|
||||
For Docker CLI, run your container with:
|
||||
|
||||
|
|
@ -45,11 +51,15 @@ security_opt:
|
|||
- seccomp=unconfined
|
||||
```
|
||||
|
||||
## My host is incompatible with images based on rdesktop {#rdesktop}
|
||||
??? faq "My host is incompatible with images based on rdesktop"
|
||||
|
||||
##### My host is incompatible with images based on rdesktop { #rdesktop }
|
||||
|
||||
=== "Description"
|
||||
|
||||
Some x86_64 hosts have issues running rdesktop based images even with the latest Docker version due to syscalls that are unknown to Docker.
|
||||
|
||||
### Symptoms
|
||||
=== "Symptoms"
|
||||
|
||||
If your host is affected you may see errors in your containers such as:
|
||||
|
||||
|
|
@ -57,7 +67,7 @@ If your host is affected you may see errors in your containers such as:
|
|||
Failed to close file descriptor for child process (Operation not permitted)
|
||||
```
|
||||
|
||||
### Resolution
|
||||
=== "Resolution"
|
||||
|
||||
For Docker CLI, run your container with:
|
||||
|
||||
|
|
@ -70,7 +80,11 @@ For Docker Compose, run your container with:
|
|||
- seccomp=unconfined
|
||||
```
|
||||
|
||||
## My host is incompatible with images based on Ubuntu Focal and Alpine 3.13 and later {#libseccomp}
|
||||
??? 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 }
|
||||
|
||||
=== "Description"
|
||||
|
||||
This only affects 32 bit installs of distros based on Debian Buster.
|
||||
|
||||
|
|
@ -80,13 +94,21 @@ This is due to a bug in the libseccomp2 library (dependency of Docker itself), w
|
|||
|
||||
You have a few options as noted below. Options 1 is short-term, while option 2 is considered the best option if you don't plan to reinstall the device (option 3).
|
||||
|
||||
### Resolution
|
||||
=== "Symptoms"
|
||||
|
||||
- 502 errors in __Jellyfin__ as seen in [linuxserver/docker-jellyfin#71](https://github.com/linuxserver/docker-jellyfin/issues/71)
|
||||
- `Error starting framework core` messages in the docker log for __Plex__. [linuxserver/docker-plex#247](https://github.com/linuxserver/docker-plex/issues/247)
|
||||
- No WebUI for __Radarr__, even though the container is running. [linuxserver/docker-radarr#118](https://github.com/linuxserver/docker-radarr/issues/118)
|
||||
- Images based on our Nginx base-image(Nextcloud, SWAG, Nginx, etc.) fails to generate a certificate, with a message similar to `error getting time:crypto/asn1/a_time.c:330`
|
||||
- `docker exec <container-name> date` returns 1970
|
||||
|
||||
=== "Resolution"
|
||||
|
||||
If you decide to do option 1 or 2, you should just need to restart the container after confirming you have libseccomp2.4.4 installed.
|
||||
|
||||
If 1 or 2 did not work, ensure your Docker install is at least version 20.10.0, [refer to the official Docker docs for installation.](https://docs.docker.com/engine/install/debian/)
|
||||
|
||||
#### Manual patch
|
||||
<h4>Manual patch</h4>
|
||||
|
||||
Manually install an updated version of the library with dpkg.
|
||||
|
||||
|
|
@ -98,7 +120,7 @@ sudo dpkg -i libseccomp2_2.4.4-1~bpo10+1_armhf.deb
|
|||
!!! info
|
||||
This url may have been updated. Find the latest by browsing [here](http://ftp.us.debian.org/debian/pool/main/libs/libseccomp/).
|
||||
|
||||
#### Automatic Patch
|
||||
<h4>Automatic Patch</h4>
|
||||
|
||||
Add the backports repo for DebianBuster. As seen [here](https://github.com/linuxserver/docker-jellyfin/issues/71#issuecomment-733621693).
|
||||
|
||||
|
|
@ -109,7 +131,7 @@ sudo apt update
|
|||
sudo apt install -t buster-backports libseccomp2
|
||||
```
|
||||
|
||||
#### Move to a compatible OS
|
||||
<h4>Move to a compatible OS</h4>
|
||||
|
||||
Reinstall/update your OS to a version that still gets updates.
|
||||
|
||||
|
|
@ -119,19 +141,15 @@ Reinstall/update your OS to a version that still gets updates.
|
|||
!!! info
|
||||
RaspberryPI OS (formerly Raspbian) Can be upgraded to run with a 64bit kernel
|
||||
|
||||
### Symptoms
|
||||
??? faq "My host filesystem is incompatible with my docker storage driver"
|
||||
|
||||
- 502 errors in __Jellyfin__ as seen in [linuxserver/docker-jellyfin#71](https://github.com/linuxserver/docker-jellyfin/issues/71)
|
||||
- `Error starting framework core` messages in the docker log for __Plex__. [linuxserver/docker-plex#247](https://github.com/linuxserver/docker-plex/issues/247)
|
||||
- No WebUI for __Radarr__, even though the container is running. [linuxserver/docker-radarr#118](https://github.com/linuxserver/docker-radarr/issues/118)
|
||||
- Images based on our Nginx base-image(Nextcloud, SWAG, Nginx, etc.) fails to generate a certificate, with a message similar to `error getting time:crypto/asn1/a_time.c:330`
|
||||
- `docker exec <container-name> date` returns 1970
|
||||
##### My host filesystem is incompatible with my docker storage driver { #storage }
|
||||
|
||||
## My host filesystem is incompatible with my docker storage driver {#storage}
|
||||
=== "Description"
|
||||
|
||||
Some host file systems types are not compatible with the default storage driver of docker (overlay2)
|
||||
|
||||
### Symptoms
|
||||
=== "Symptoms"
|
||||
|
||||
If your host is affected you may see errors in your containers such as:
|
||||
|
||||
|
|
@ -145,14 +163,16 @@ or
|
|||
Directory not empty. This directory contains an empty ignorecommands sub-directory
|
||||
```
|
||||
|
||||
### Resolution
|
||||
=== "Resolution"
|
||||
|
||||
As shown in [Docker docs](https://docs.docker.com/storage/storagedriver/select-storage-driver/#supported-backing-filesystems)
|
||||
|
||||
A host filesystem of zfs requires a docker storage driver of zfs and a host file system of btrfs requires a docker storage driver of btrfs.
|
||||
Correcting this oversight will resolve the issue. This is not something that a container change will resolve.
|
||||
|
||||
## What is lscr.io {#lscr}
|
||||
??? faq "What is lscr.io"
|
||||
|
||||
##### 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).
|
||||
|
||||
|
|
@ -164,7 +184,9 @@ We have some blog posts related to how we utilize Scarf:
|
|||
- [Unravelling Some Stats](https://www.linuxserver.io/blog/unravelling-some-stats)
|
||||
- [Wrap Up Warm For Winter](https://www.linuxserver.io/blog/wrap-up-warm-for-the-winter)
|
||||
|
||||
### I cannot connect to lscr.io {#lscr-no-connect}
|
||||
??? faq "I cannot connect to lscr.io"
|
||||
|
||||
##### 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.
|
||||
|
||||
|
|
@ -196,9 +218,11 @@ nslookup lscr.io
|
|||
|
||||
If you only got a response from ghcr, chances are that Scarf is on the blocklist.
|
||||
|
||||
## I want to reverse proxy an application which defaults to https with a self-signed certificate {#strict-proxy}
|
||||
??? faq "I want to reverse proxy an application which defaults to https with a self-signed certificate"
|
||||
|
||||
### Traefik {#strict-proxy-traefik}
|
||||
##### I want to reverse proxy an application which defaults to https with a self-signed certificate { #strict-proxy }
|
||||
|
||||
=== "Traefik"
|
||||
|
||||
In this example, we will configure a serverTransport rule we can apply to a service, as well as telling Traefik to use https on the backend for the service.
|
||||
|
||||
|
|
@ -218,7 +242,9 @@ Then on our `foo` service we tell it to use this rule, as well as telling Traefi
|
|||
- traefik.http.services.foo.loadbalancer.server.scheme=https
|
||||
```
|
||||
|
||||
## Why does LinuxServer.io recommend to use docker-compose over Portainer? {#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 }
|
||||
|
||||
Portainer has many issues which make it hard for us to support, such as:
|
||||
|
||||
|
|
@ -229,15 +255,19 @@ Portainer has many issues which make it hard for us to support, such as:
|
|||
- Inconsistent compose implementations on different architectures
|
||||
- Incorrectly applying environment variables on container upgrades
|
||||
|
||||
## Inexplicable issues when running ubuntu {#snap}
|
||||
??? faq "Inexplicable issues when running ubuntu"
|
||||
|
||||
##### Inexplicable issues when running ubuntu { #snap }
|
||||
|
||||
=== "Description"
|
||||
|
||||
Many users have been facing issues that are simply inexplicable. The logs show no problems, the compose is fine, eventually it turns out they've installed the SNAP version of docker which is the source of the issues.
|
||||
|
||||
### Symptoms
|
||||
=== "Symptoms"
|
||||
|
||||
It's difficult to identify the symptoms, but if you are running ubuntu and believe you have done everything correctly, check for SNAP docker.
|
||||
|
||||
### Resolution
|
||||
=== "Resolution"
|
||||
|
||||
First the user must be on an appropriate version of ubuntu to face this issue (as far as I am aware)
|
||||
|
||||
|
|
|
|||
|
|
@ -0,0 +1,19 @@
|
|||
.md-typeset .admonition.faq,
|
||||
.md-typeset details.faq {
|
||||
border-color: rgb(77, 77, 77);
|
||||
}
|
||||
.md-typeset details.faq > h5 {
|
||||
visibility: hidden;
|
||||
height: 0;
|
||||
margin-top: 0;
|
||||
margin-bottom: 0;
|
||||
}
|
||||
.md-typeset .faq > .admonition-title,
|
||||
.md-typeset .faq > summary {
|
||||
background-color: transparent;
|
||||
padding-left: 12px;
|
||||
}
|
||||
.md-typeset .faq > .admonition-title::before,
|
||||
.md-typeset .faq > summary::before {
|
||||
visibility: hidden;
|
||||
}
|
||||
|
|
@ -53,10 +53,18 @@ extra:
|
|||
link: https://mastodon.linuxserver.io/@linuxserver
|
||||
- icon: fontawesome/brands/bluesky
|
||||
link: https://bsky.app/profile/linuxserver.io
|
||||
extra_css:
|
||||
- stylesheets/extra.css
|
||||
extra_javascript:
|
||||
- https://unpkg.com/tablesort@5.3.0/dist/tablesort.min.js
|
||||
- javascripts/tablesort.js
|
||||
markdown_extensions:
|
||||
- pymdownx.tabbed:
|
||||
combine_header_slug: true
|
||||
alternate_style: true
|
||||
slugify: !!python/object/apply:pymdownx.slugs.slugify
|
||||
kwds:
|
||||
case: lower
|
||||
- admonition
|
||||
- pymdownx.details
|
||||
- pymdownx.escapeall
|
||||
|
|
|
|||
Ładowanie…
Reference in New Issue