{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"]},"docs":[{"location":"","title":"Introduction","text":"<p>Welcome to the home of the LinuxServer.io documentation! It is our goal to ensure that all of our images are properly documented with all of the relevant information, in order to help our users get started. In addition to individual set up guides for each image, there is also general information, and best practices, pertaining to running Docker containers.</p>"},{"location":"#want-to-get-hold-of-the-team","title":"Want to get hold of the team?","text":"<p>The team resides primarily in our Discord server. We also have a forum if chat isn't your thing.</p> Where Link Discord https://discord.gg/YWrKVTn Forum https://discourse.linuxserver.io <p>For those interested in our CI environment via Jenkins: https://ci.linuxserver.io/</p>"},{"location":"FAQ/","title":"FAQ","text":"<p>Here resides some Frequently Asked Questions.</p>"},{"location":"FAQ/#jammy","title":"My host is incompatible with images based on Ubuntu Jammy","text":"<p>Some x86_64 hosts running older versions of the Docker engine are not compatible with some images based on Ubuntu Jammy.</p>"},{"location":"FAQ/#symptoms","title":"Symptoms","text":"<p>If your host is affected you may see errors in your containers such as:</p> <pre><code>ERROR - Unable to determine java version; make sure Java is installed and callable\n</code></pre> <p>Or</p> <pre><code>Failed to create CoreCLR, HRESULT: 0x80070008\n</code></pre> <p>Or</p> <pre><code>WARNING :: MAIN : webStart.py:initialize:249 : can't start new thread\n</code></pre>"},{"location":"FAQ/#resolution","title":"Resolution","text":""},{"location":"FAQ/#long-term-fix","title":"Long-Term Fix","text":"<p>Upgrade your Docker engine to at least version <code>20.10.10</code>. Refer to the official Docker docs for installation/update details.</p>"},{"location":"FAQ/#short-term-fix","title":"Short-Term Fix","text":"<p>For Docker CLI, run your container with:</p> <p><code>--security-opt seccomp=unconfined</code></p> <p>For Docker Compose, run your container with:</p> <pre><code>security_opt:\n - seccomp=unconfined\n</code></pre>"},{"location":"FAQ/#rdesktop","title":"My host is incompatible with images based on rdesktop","text":"<p>Some x86_64 hosts have issues running rdesktop based images even with the latest Docker version due to syscalls that are unknown to Docker.</p>"},{"location":"FAQ/#symptoms_1","title":"Symptoms","text":"<p>If your host is affected you may see errors in your containers such as:</p> <pre><code>Failed to close file descriptor for child process (Operation not permitted)\n</code></pre>"},{"location":"FAQ/#resolution_1","title":"Resolution","text":"<p>For Docker CLI, run your container with:</p> <p><code>--security-opt seccomp=unconfined</code></p> <p>For Docker Compose, run your container with:</p> <pre><code> security_opt:\n - seccomp=unconfined\n</code></pre>"},{"location":"FAQ/#libseccomp","title":"My host is incompatible with images based on Ubuntu Focal and Alpine 3.13 and later","text":"<p>This only affects 32 bit installs of distros based on Debian Buster.</p> <p>This is due to a bug in the libseccomp2 library (dependency of Docker itself), which is fixed. However, it's not pushed to all the repositories.</p> <p>A GitHub issue tracking this</p> <p>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).</p>"},{"location":"FAQ/#resolution_2","title":"Resolution","text":"<p>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.</p> <p>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.</p>"},{"location":"FAQ/#manual-patch","title":"Manual patch","text":"<p>Manuallyinstallanupdatedversionofthelibrarywithdpkg.</p><pre><code>wgethttp://ftp.us.debian.org/debian/pool/main/libs/libseccomp/libse
