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

Merge branch 'master' into ghcrupdate

pull/52/head
Adam 2022-05-21 11:33:27 +01:00 zatwierdzone przez GitHub
rodzic 7989cf798d 561bdfdeb8
commit edeb8349ff
Nie znaleziono w bazie danych klucza dla tego podpisu
ID klucza GPG: 4AEE18F83AFDEB23
143 zmienionych plików z 2020 dodań i 1771 usunięć
Pokaż statystyki Ściągnij plik aktualizacji Ściągnij plik porównania Expand all files Collapse all files

43
FAQ.md
Wyświetl plik

@ -2,6 +2,49 @@
Here will some Frequently Asked Questions reside
## My host is incompatible with images based on Ubuntu Jammy {#jammy}
Some x86_64 hosts running older versions of the Docker engine are not compatible with some images based on Ubuntu Jammy.
### Symptoms
If your host is affected you may see errors in your containers such as:
```shell
ERROR - Unable to determine java version; make sure Java is installed and callable
```
Or
```shell
Failed to create CoreCLR, HRESULT: 0x80070008
```
Or
```shell
WARNING :: MAIN : webStart.py:initialize:249 : can't start new thread
```
### Resolution
#### Option 1 (Long-Term Fix)
Upgrade your Docker engine install to at least version `20.10.10`. [Refer to the official Docker docs for installation/update details.](https://docs.docker.com/engine/install)
#### Option 2 (Short-Term Fix)
For Docker CLI, run your container with:
`--security-opt seccomp=unconfined`
For Docker Compose, run your container with:
```yaml
security_opt:
- seccomp=unconfined
```
## My host is incompatible with images based on Ubuntu Focal and Alpine 3.13 and later {#libseccomp}
This only affects 32 bit installs of distros based on Debian Buster.

53
general/awesome-lsio.md
Wyświetl plik

@ -11,14 +11,12 @@
| [netbox](https://github.com/linuxserver/docker-netbox/) | [netbox](https://github.com/netbox-community/netbox) is an IP address management (IPAM) and data center infrastructure management (DCIM) tool. Initially conceived by the network engineering team at DigitalOcean, NetBox was developed specifically to address the needs of network and infrastructure engineers. It is intended to function as a domain-specific source of truth for network operations. |
| [openssh-server](https://github.com/linuxserver/docker-openssh-server/) | [openssh-server](https://www.openssh.com/) is a sandboxed environment that allows ssh access without giving keys to the entire server. |
| [snipe-it](https://github.com/linuxserver/docker-snipe-it/) | [snipe-it](https://github.com/snipe/snipe-it) makes asset management easy. It was built by people solving real-world IT and asset management problems, and a solid UX has always been a top priority. Straightforward design and bulk actions mean getting things done faster. |
| [taisun](https://github.com/linuxserver/docker-taisun/) | [taisun](https://www.taisun.io/) is an application for a Docker enabled device with an emphasis on providing a web based interface for managing a single server. |
## Audiobooks
| Container | Description |
| --------- | ----------- |
| [booksonic](https://github.com/linuxserver/docker-booksonic/) | [booksonic](http://booksonic.org) is a server and an app for streaming your audiobooks to any pc or android phone. Most of the functionality is also availiable on other platforms that have apps for subsonic. |
| [booksonic-air](https://github.com/linuxserver/docker-booksonic-air/) | [booksonic-air](http://booksonic.org) is a platform for accessing the audibooks you own wherever you are. At the moment the platform consists of |
| [booksonic-air](https://github.com/linuxserver/docker-booksonic-air/) | [booksonic-air](http://booksonic.org) is a platform for accessing the audiobooks you own wherever you are. At the moment the platform consists of |
## Automation
@ -26,7 +24,7 @@
| --------- | ----------- |
| [domoticz](https://github.com/linuxserver/docker-domoticz/) | [domoticz](https://www.domoticz.com) is a Home Automation System that lets you monitor and configure various devices like: Lights, Switches, various sensors/meters like Temperature, Rain, Wind, UV, Electra, Gas, Water and much more. Notifications/Alerts can be sent to any mobile device. |
| [habridge](https://github.com/linuxserver/docker-habridge/) | [habridge](http://bwssystems.com/#/habridge) emulates Philips Hue API to other home automation gateways such as an Amazon Echo/Dot Gen 1 (gen 2 has issues discovering ha-bridge) or other systems that support Philips Hue. The Bridge handles basic commands such as "On", "Off" and "brightness" commands of the hue protocol. This bridge can control most devices that have a distinct API. |
| [homeassistant](https://github.com/linuxserver/docker-homeassistant/) | [homeassistant](https://www.home-assistant.io/) is open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts. Perfect to run on a Raspberry Pi or a local server. |
| [homeassistant](https://github.com/linuxserver/docker-homeassistant/) | [Home Assistant Core](https://www.home-assistant.io/) - Open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts. Perfect to run on a Raspberry Pi or a local server. |
| [kanzi](https://github.com/linuxserver/docker-kanzi/) | [kanzi](https://lexigr.am/), formerly titled Kodi-Alexa, this custom skill is the ultimate voice remote control for navigating Kodi. It can do anything you can think of (100+ intents). This container also contains lexigram-cli to setup Kanzi with an Amazon Developer Account and automatically deploy it to Amazon. |
## Backup
@ -47,7 +45,7 @@
| [cops](https://github.com/linuxserver/docker-cops/) | [cops](http://blog.slucas.fr/en/oss/calibre-opds-php-server) by Sébastien Lucas, stands for Calibre OPDS (and HTML) Php Server. |
| [lazylibrarian](https://github.com/linuxserver/docker-lazylibrarian/) | [lazylibrarian](https://lazylibrarian.gitlab.io/) is a program to follow authors and grab metadata for all your digital reading needs. It uses a combination of Goodreads Librarything and optionally GoogleBooks as sources for author info and book info. This container is based on the DobyTang fork. |
| [mylar3](https://github.com/linuxserver/docker-mylar3/) | [mylar3](https://github.com/mylar3/mylar3) is an automated Comic Book downloader (cbr/cbz) for use with NZB and torrents written in python. It supports SABnzbd, NZBGET, and many torrent clients in addition to DDL. |
| [readarr](https://github.com/linuxserver/docker-readarr/) | No description |
| [readarr](https://github.com/linuxserver/docker-readarr/) | [readarr](https://github.com/Readarr/Readarr) - Book Manager and Automation (Sonarr for Ebooks) |
| [ubooquity](https://github.com/linuxserver/docker-ubooquity/) | [ubooquity](https://vaemendis.net/ubooquity/) is a free, lightweight and easy-to-use home server for your comics and ebooks. Use it to access your files from anywhere, with a tablet, an e-reader, a phone or a computer. |
## Cloud
@ -60,7 +58,9 @@
| Container | Description |
| --------- | ----------- |
| [gmail-order-bot](https://github.com/linuxserver/docker-gmail-order-bot/) | [gmail-order-bot](https://developers.google.com/gmail/api) - A bot used to leverage a Gmail account as an order messaging service to consume email orders from [Nano Checkout](https://github.com/linuxserver/nano-checkout) and process them using any custom logic you choose. |
| [nano](https://github.com/linuxserver/docker-nano/) | [nano](https://nano.org/) is a digital payment protocol designed to be accessible and lightweight, with a focus on removing inefficiencies present in other cryptocurrencies. With ultrafast transactions and zero fees on a secure, green and decentralized network, this makes Nano ideal for everyday transactions. |
| [nano-discord-bot](https://github.com/linuxserver/docker-nano-discord-bot/) | [nano-discord-bot](https://discord.com/developers/docs/intro) - A bot used to hook into a [self hosted Nano RPC endpoint](https://hub.docker.com/r/linuxserver/nano) and discord server to Distribute funds from a faucet account. |
| [nano-wallet](https://github.com/linuxserver/docker-nano-wallet/) | [nano-wallet](https://nano.org/) is a digital payment protocol designed to be accessible and lightweight, with a focus on removing inefficiencies present in other cryptocurrencies. With ultrafast transactions and zero fees on a secure, green and decentralized network, this makes Nano ideal for everyday transactions. |
## DNS
@ -75,7 +75,6 @@
| Container | Description |
| --------- | ----------- |
| [clarkson](https://github.com/linuxserver/docker-clarkson/) | [clarkson](https://github.com/linuxserver/Clarkson) is a web-based dashboard application that gives you a neat and clean interface for logging your fuel fill-ups for all of your vehicles. The application has full multi-user support, as well as multiple vehicles per user. Whenever you fill-up your car or motorcycle, keep the receipt and record the data in Clarkson. |
| [heimdall](https://github.com/linuxserver/docker-heimdall/) | [heimdall](https://heimdall.site) is a way to organise all those links to your most used web sites and web applications in a simple way. |
| [muximux](https://github.com/linuxserver/docker-muximux/) | [muximux](https://github.com/mescon/Muximux) is a lightweight portal to view & manage your HTPC apps without having to run anything more than a PHP enabled webserver. With Muximux you don't need to keep multiple tabs open, or bookmark the URL to all of your apps. |
@ -94,7 +93,6 @@
| --------- | ----------- |
| [docker-compose](https://github.com/linuxserver/docker-docker-compose/) | No description |
| [fleet](https://github.com/linuxserver/docker-fleet/) | [fleet](https://github.com/linuxserver/fleet) provides an online web interface which displays a set of maintained images from one or more owned repositories. |
| [mods](https://github.com/linuxserver/docker-mods/) | No description |
## Documents
@ -102,6 +100,7 @@
| --------- | ----------- |
| [libreoffice](https://github.com/linuxserver/docker-libreoffice/) | [LibreOffice](https://www.libreoffice.org/) is a free and powerful office suite, and a successor to OpenOffice.org (commonly known as OpenOffice). Its clean interface and feature-rich tools help you unleash your creativity and enhance your productivity. |
| [paperless-ng](https://github.com/linuxserver/docker-paperless-ng/) | [paperless-ng](https://github.com/jonaswinkler/paperless-ng) is an application by Daniel Quinn and contributors that indexes your scanned documents and allows you to easily search for documents and store metadata alongside your documents." |
| [paperless-ngx](https://github.com/linuxserver/docker-paperless-ngx/) | [paperless-ngx](https://github.com/paperless-ngx/paperless-ngx) is an application by Daniel Quinn and contributors that indexes your scanned documents and allows you to easily search for documents and store metadata alongside your documents." |
| [papermerge](https://github.com/linuxserver/docker-papermerge/) | [papermerge](https://www.papermerge.com/) is an open source document management system (DMS) primarily designed for archiving and retrieving your digital documents. Instead of having piles of paper documents all over your desk, office or drawers - you can quickly scan them and configure your scanner to directly upload to Papermerge DMS." |
## Downloaders
@ -111,7 +110,7 @@
| [deluge](https://github.com/linuxserver/docker-deluge/) | [deluge](http://deluge-torrent.org/) is a lightweight, Free Software, cross-platform BitTorrent client. |
| [nntp2nntp](https://github.com/linuxserver/docker-nntp2nntp/) | [nntp2nntp](https://github.com/linuxserver/nntp2nntp) proxy allow you to use your NNTP Account from multiple systems, each with own user name and password. It fully supports SSL and you can also limit the access to proxy with SSL certificates. nntp2nntp proxy is very simple and pretty fast. |
| [nzbget](https://github.com/linuxserver/docker-nzbget/) | [nzbget](http://nzbget.net/) is a usenet downloader, written in C++ and designed with performance in mind to achieve maximum download speed by using very little system resources. |
| [pyload](https://github.com/linuxserver/docker-pyload/) | [pyload](https://pyload.net/) is a Free and Open Source download manager written in Python and designed to be extremely lightweight, easily extensible and fully manageable via web. |
| [pyload-ng](https://github.com/linuxserver/docker-pyload-ng/) | [pyLoad](https://pyload.net/) is a Free and Open Source download manager written in Python and designed to be extremely lightweight, easily extensible and fully manageable via web. |
| [qbittorrent](https://github.com/linuxserver/docker-qbittorrent/) | The [qbittorrent](https://www.qbittorrent.org/) project aims to provide an open-source software alternative to µTorrent. qBittorrent is based on the Qt toolkit and libtorrent-rasterbar library. |
| [sabnzbd](https://github.com/linuxserver/docker-sabnzbd/) | [sabnzbd](http://sabnzbd.org/) makes Usenet as simple and streamlined as possible by automating everything we can. All you have to do is add an .nzb. SABnzbd takes over from there, where it will be automatically downloaded, verified, repaired, extracted and filed away with zero human interaction. |
| [transmission](https://github.com/linuxserver/docker-transmission/) | [transmission](https://www.transmissionbt.com/) is designed for easy, powerful use. Transmission has the features you want from a BitTorrent client: encryption, a web interface, peer exchange, magnet links, DHT, µTP, UPnP and NAT-PMP port forwarding, webseed support, watch directories, tracker editing, global and per-torrent speed limits, and more. |
@ -139,6 +138,12 @@
| [snapdrop](https://github.com/linuxserver/docker-snapdrop/) | [snapdrop](https://github.com/RobinLinus/snapdrop) A local file sharing in your browser. Inspired by Apple's Airdrop. |
| [xbackbone](https://github.com/linuxserver/docker-xbackbone/) | [xbackbone](https://github.com/SergiX44/XBackBone) is a simple, self-hosted, lightweight PHP file manager that support the instant sharing tool ShareX and *NIX systems. It supports uploading and displaying images, GIF, video, code, formatted text, and file downloading and uploading. Also have a web UI with multi user management, past uploads history and search support. |
## Finance
| Container | Description |
| --------- | ----------- |
| [budge](https://github.com/linuxserver/docker-budge/) | [budge](https://github.com/linuxserver/budge) is an open source 'budgeting with envelopes' personal finance app. |
## Games
| Container | Description |
@ -146,6 +151,13 @@
| [emulatorjs](https://github.com/linuxserver/docker-emulatorjs/) | [emulatorjs](https://github.com/linuxserver/emulatorjs) - In browser web based emulation portable to nearly any device for many retro consoles. A mix of emulators is used between Libretro and EmulatorJS. |
| [minetest](https://github.com/linuxserver/docker-minetest/) | [minetest](http://www.minetest.net/) (server) is a near-infinite-world block sandbox game and a game engine, inspired by InfiniMiner, Minecraft, and the like. |
## Graphics
| Container | Description |
| --------- | ----------- |
| [blender](https://github.com/linuxserver/docker-blender/) | [Blender](https://www.blender.org/) is a free and open-source 3D computer graphics software toolset used for creating animated films, visual effects, art, 3D printed models, motion graphics, interactive 3D applications, virtual reality, and computer games. **This image does not support GPU rendering out of the box only accelerated workspace experience** |
| [kdenlive](https://github.com/linuxserver/docker-kdenlive/) | [Kdenlive](https://kdenlive.org/) is a powerful free and open source cross-platform video editing program made by the KDE community. Feature rich and production ready. |
## IRC
| Container | Description |
@ -164,16 +176,15 @@
| --------- | ----------- |
| [jackett](https://github.com/linuxserver/docker-jackett/) | [jackett](https://github.com/Jackett/Jackett) works as a proxy server: it translates queries from apps (Sonarr, SickRage, CouchPotato, Mylar, etc) into tracker-site-specific http queries, parses the html response, then sends results back to the requesting software. This allows for getting recent uploads (like RSS) and performing searches. Jackett is a single repository of maintained indexer scraping & translation logic - removing the burden from other apps. |
| [nzbhydra2](https://github.com/linuxserver/docker-nzbhydra2/) | [nzbhydra2](https://github.com/theotherp/nzbhydra2) is a meta search application for NZB indexers, the "spiritual successor" to NZBmegasearcH, and an evolution of the original application [NZBHydra](https://github.com/theotherp/nzbhydra). |
| [prowlarr](https://github.com/linuxserver/docker-prowlarr/) | No description |
| [prowlarr](https://github.com/linuxserver/docker-prowlarr/) | [prowlarr](https://github.com/Prowlarr/Prowlarr) is a indexer manager/proxy built on the popular arr .net/reactjs base stack to integrate with your various PVR apps. Prowlarr supports both Torrent Trackers and Usenet Indexers. It integrates seamlessly with Sonarr, Radarr, Lidarr, and Readarr offering complete management of your indexers with no per app Indexer setup required (we do it all). |
## Media Management
| Container | Description |
| --------- | ----------- |
| [bazarr](https://github.com/linuxserver/docker-bazarr/) | [bazarr](https://www.bazarr.media/) is a companion application to Sonarr and Radarr. It can manage and download subtitles based on your requirements. You define your preferences by TV show or movie and Bazarr takes care of everything for you. |
| [couchpotato](https://github.com/linuxserver/docker-couchpotato/) | [couchpotato](https://couchpota.to/) is an automatic NZB and torrent downloader. You can keep a `movies I want` list and it will search for NZBs/torrents of these movies every X hours. Once a movie is found, it will send it to SABnzbd or download the torrent to a specified directory. |
| [kodi-headless](https://github.com/linuxserver/docker-kodi-headless/) | No description |
| [medusa](https://github.com/linuxserver/docker-medusa/) | [medusa](https://pymedusa.com/) is an automatic Video Library Manager for TV Shows. It watches for new episodes of your favorite shows, and when they are posted it does its magic. |
| [plex-meta-manager](https://github.com/linuxserver/docker-plex-meta-manager/) | [plex-meta-manager](https://github.com/meisnate12/Plex-Meta-Manager) is a Python 3 script that can be continuously run using YAML configuration files to update on a schedule the metadata of the movies, shows, and collections in your libraries as well as automatically build collections based on various methods all detailed in the wiki. |
| [radarr](https://github.com/linuxserver/docker-radarr/) | [radarr](https://github.com/Radarr/Radarr) - A fork of Sonarr to work with movies à la Couchpotato. |
| [sickchill](https://github.com/linuxserver/docker-sickchill/) | [sickchill](https://github.com/SickChill/SickChill) is an Automatic Video Library Manager for TV Shows. It watches for new episodes of your favorite shows, and when they are posted it does its magic. |
| [sickgear](https://github.com/linuxserver/docker-sickgear/) | [SickGear](https://github.com/sickgear/sickgear) provides management of TV shows and/or Anime, it detects new episodes, links downloader apps, and more.. |
@ -191,9 +202,9 @@
| Container | Description |
| --------- | ----------- |
| [doplarr](https://github.com/linuxserver/docker-doplarr/) | [doplarr](https://github.com/kiranshila/Doplarr) is an *arr request bot for Discord." |
| [ombi](https://github.com/linuxserver/docker-ombi/) | [ombi](https://ombi.io) allows you to host your own Plex Request and user management system. |
| [overseerr](https://github.com/linuxserver/docker-overseerr/) | [overseerr](https://overseerr.dev/) is a request management and media discovery tool built to work with your existing Plex ecosystem. |
| [requestrr](https://github.com/linuxserver/docker-requestrr/) | [requestrr](https://github.com/darkalfx/requestrr) is a chatbot used to simplify using services like Sonarr/Radarr/Ombi via the use of chat. |
## Media Tools
@ -214,10 +225,8 @@
| Container | Description |
| --------- | ----------- |
| [apprise-api](https://github.com/linuxserver/docker-apprise-api/) | [apprise-api](https://github.com/caronc/apprise-api) Takes advantage of [Apprise](https://github.com/caronc/apprise) through your network with a user-friendly API. |
| [diskover](https://github.com/linuxserver/docker-diskover/) | [diskover](https://github.com/diskoverdata/diskover-community) is an open source file system indexer that uses Elasticsearch to index and manage data across heterogeneous storage systems. |
| [healthchecks](https://github.com/linuxserver/docker-healthchecks/) | [healthchecks](https://github.com/healthchecks/healthchecks) is a watchdog for your cron jobs. It's a web server that listens for pings from your cron jobs, plus a web interface. |
| [librespeed](https://github.com/linuxserver/docker-librespeed/) | [librespeed](https://github.com/librespeed/speedtest) is a very lightweight Speedtest implemented in Javascript, using XMLHttpRequest and Web Workers. |
| [scrutiny](https://github.com/linuxserver/docker-scrutiny/) | [scrutiny](https://github.com/AnalogJ/scrutiny) WebUI for smartd S.M.A.R.T monitoring. Scrutiny is a Hard Drive Health Dashboard & Monitoring solution, merging manufacturer provided S.M.A.R.T metrics with real-world failure rates from Backblaze. |
| [smokeping](https://github.com/linuxserver/docker-smokeping/) | [smokeping](https://oss.oetiker.ch/smokeping/) keeps track of your network latency. For a full example of what this application is capable of visit [UCDavis](http://smokeping.ucdavis.edu/cgi-bin/smokeping.fcgi). |
| [syslog-ng](https://github.com/linuxserver/docker-syslog-ng/) | [syslog-ng](https://www.syslog-ng.com/products/open-source-log-management/) allows you to flexibly collect, parse, classify, rewrite and correlate logs from across your infrastructure and store or route them to log analysis tools. |
@ -225,7 +234,6 @@
| Container | Description |
| --------- | ----------- |
| [airsonic](https://github.com/linuxserver/docker-airsonic/) | [airsonic](https://github.com/airsonic/airsonic) is a free, web-based media streamer, providing ubiquitious access to your music. Use it to share your music with friends, or to listen to your own music while at work. You can stream to multiple players simultaneously, for instance to one player in your kitchen and another in your living room. |
| [airsonic-advanced](https://github.com/linuxserver/docker-airsonic-advanced/) | [airsonic-advanced](https://github.com/airsonic-advanced/airsonic-advanced) is a free, web-based media streamer, providing ubiquitious access to your music. Use it to share your music with friends, or to listen to your own music while at work. You can stream to multiple players simultaneously, for instance to one player in your kitchen and another in your living room. |
| [audacity](https://github.com/linuxserver/docker-audacity/) | [Audacity](https://www.audacityteam.org/) is an easy-to-use, multi-track audio editor and recorder. Developed by a group of volunteers as open source. |
| [beets](https://github.com/linuxserver/docker-beets/) | [beets](http://beets.io/) is a music library manager and not, for the most part, a music player. It does include a simple player plugin and an experimental Web-based player, but it generally leaves actual sound-reproduction to specialized tools. |
@ -238,7 +246,7 @@
| Container | Description |
| --------- | ----------- |
| [unifi-controller](https://github.com/linuxserver/docker-unifi-controller/) | The [unifi-controller](https://www.ubnt.com/enterprise/#unifi) Controller software is a powerful, enterprise wireless software engine ideal for high-density client deployments requiring low latency and high uptime performance. |
| [unifi-controller](https://github.com/linuxserver/docker-unifi-controller/) | The [unifi-controller](https://www.ubnt.com/enterprise/#unifi) software is a powerful, enterprise wireless software engine ideal for high-density client deployments requiring low latency and high uptime performance. |
| [wireshark](https://github.com/linuxserver/docker-wireshark/) | [Wireshark](https://www.wireshark.org/) is the world’s foremost and widely-used network protocol analyzer. It lets you see what’s happening on your network at a microscopic level and is the de facto (and often de jure) standard across many commercial and non-profit enterprises, government agencies, and educational institutions. Wireshark development thrives thanks to the volunteer contributions of networking experts around the globe and is the continuation of a project started by Gerald Combs in 1998. |
## Photos
@ -279,9 +287,9 @@
| Container | Description |
| --------- | ----------- |
| [guacd](https://github.com/linuxserver/docker-guacd/) | [guacd](https://guacamole.apache.org/) - Apache Guacamole is a clientless remote desktop gateway. It supports standard protocols like VNC, RDP, and SSH. This container is only the backend server component needed to use The official or 3rd party HTML5 frontends. |
| [rdesktop](https://github.com/linuxserver/docker-rdesktop/) | [rdesktop](http://xrdp.org/) - Ubuntu based containers containing full desktop environments in officially supported flavors accessible via RDP. |
| [rdesktop](https://github.com/linuxserver/docker-rdesktop/) | [rdesktop](http://xrdp.org/) - Containers containing full desktop environments in many popular flavors for Alpine, Ubuntu, Arch, and Fedora accessible via RDP. |
| [remmina](https://github.com/linuxserver/docker-remmina/) | [Remmina](https://remmina.org/) is a remote desktop client written in GTK, aiming to be useful for system administrators and travellers, who need to work with lots of remote computers in front of either large or tiny screens. Remmina supports multiple network protocols, in an integrated and consistent user interface. Currently RDP, VNC, SPICE, NX, XDMCP, SSH and EXEC are supported. |
| [webtop](https://github.com/linuxserver/docker-webtop/) | [webtop](https://github.com/linuxserver/docker-webtop) - Alpine, Ubuntu, Fedora, and Arch based containers containing full desktop environments in officially supported flavors accessible via any modern web browser. |
| [webtop](https://github.com/linuxserver/docker-webtop/) | [webtop](https://github.com/linuxserver/gclient) - Alpine, Ubuntu, Fedora, and Arch based containers containing full desktop environments in officially supported flavors accessible via any modern web browser. |
## Science
@ -290,6 +298,14 @@
| [boinc](https://github.com/linuxserver/docker-boinc/) | [BOINC](https://boinc.berkeley.edu/) is a platform for high-throughput computing on a large scale (thousands or millions of computers). It can be used for volunteer computing (using consumer devices) or grid computing (using organizational resources). It supports virtualized, parallel, and GPU-based applications. |
| [foldingathome](https://github.com/linuxserver/docker-foldingathome/) | [Folding@home](https://foldingathome.org/) is a distributed computing project for simulating protein dynamics, including the process of protein folding and the movements of proteins implicated in a variety of diseases. It brings together citizen scientists who volunteer to run simulations of protein dynamics on their personal computers. Insights from this data are helping scientists to better understand biology, and providing new opportunities for developing therapeutics. |
## Storage
| Container | Description |
| --------- | ----------- |
| [diskover](https://github.com/linuxserver/docker-diskover/) | [diskover](https://github.com/diskoverdata/diskover-community) is an open source file system indexer that uses Elasticsearch to index and manage data across heterogeneous storage systems. |
| [qdirstat](https://github.com/linuxserver/docker-qdirstat/) | [QDirStat](https://github.com/shundhammer/qdirstat) Qt-based directory statistics: KDirStat without any KDE -- from the author of the original KDirStat. |
| [scrutiny](https://github.com/linuxserver/docker-scrutiny/) | [scrutiny](https://github.com/AnalogJ/scrutiny) WebUI for smartd S.M.A.R.T monitoring. Scrutiny is a Hard Drive Health Dashboard & Monitoring solution, merging manufacturer provided S.M.A.R.T metrics with real-world failure rates from Backblaze. |
## Tools
| Container | Description |
@ -308,7 +324,6 @@
| --------- | ----------- |
| [firefox](https://github.com/linuxserver/docker-firefox/) | [Firefox](https://www.mozilla.org/en-US/firefox/) Browser, also known as Mozilla Firefox or simply Firefox, is a free and open-source web browser developed by the Mozilla Foundation and its subsidiary, the Mozilla Corporation. Firefox uses the Gecko layout engine to render web pages, which implements current and anticipated web standards. |
| [grav](https://github.com/linuxserver/docker-grav/) | [grav](https://github.com/getgrav/grav/) is a Fast, Simple, and Flexible, file-based Web-platform. |
| [ipfs](https://github.com/linuxserver/docker-ipfs/) | [ipfs](https://ipfs.io/) - A peer-to-peer hypermedia protocol designed to make the web faster, safer, and more open. |
| [nginx](https://github.com/linuxserver/docker-nginx/) | [nginx](https://nginx.org/) is a simple webserver with php support. The config files reside in `/config` for easy user customization. |
| [swag](https://github.com/linuxserver/docker-swag/) | SWAG - Secure Web Application Gateway (formerly known as letsencrypt, no relation to Let's Encrypt™) sets up an Nginx webserver and reverse proxy with php support and a built-in certbot client that automates free SSL server certificate generation and renewal processes (Let's Encrypt and ZeroSSL). It also contains fail2ban for intrusion prevention. |

73
general/docker-compose.md
Wyświetl plik

@ -7,28 +7,43 @@ Compose is a tool for defining and running multi-container Docker applications.
## Installation
### Install Option 1 (recommended):
Starting with version 2, Docker started publishing `docker compose` as a go based plugin for docker (rather than a python based standalone binary). And they also publish this plugin for various arches, including x86_64, armhf and aarch64 (as opposed to the x86_64 only binaries for v1.X). Therefore we updated our recommended install option to utilize the plugin.
You can install `docker compose` via the following commands:
```
ARCH=$(uname -m) && [[ "${ARCH}" == "armv7l" ]] && ARCH="armv7"
sudo mkdir -p /usr/local/lib/docker/cli-plugins
sudo curl -SL "https://github.com/docker/compose/releases/latest/download/docker-compose-linux-${ARCH}" -o /usr/local/lib/docker/cli-plugins/docker-compose
sudo chmod +x /usr/local/lib/docker/cli-plugins/docker-compose
```
Assuming you already have docker (or at the very least docker-cli) installed, preferably from the official docker repos, running `docker compose version` should display the compose version.
If you don't have docker installed yet, we recommend installing it via the following commands:
```
curl -fsSL https://get.docker.com -o get-docker.sh
sh get-docker.sh
```
#### v1.X compatibility:
As v2 runs as a plugin instead of a standalone binary, it is invoked by `docker compose args` instead of `docker-compose args`. There are also some slight differences in how the yaml is operated as well. To make migration easier, Docker released a replacement binary for `docker-compose` on x86_64 and aarch64 platforms. More info on that can be found at the [upstream repo](https://github.com/docker/compose-switch).
### Install Option 2:
You can install docker-compose using our [docker-compose image](https://github.com/linuxserver/docker-docker-compose) via a run script. You can simply run the following commands on your system and you should have a functional install that you can call from anywhere as `docker-compose`:
```
sudo curl -L --fail https://raw.githubusercontent.com/linuxserver/docker-docker-compose/master/run.sh -o /usr/local/bin/docker-compose
sudo curl -L --fail https://raw.githubusercontent.com/linuxserver/docker-docker-compose/v2/run.sh -o /usr/local/bin/docker-compose
sudo chmod +x /usr/local/bin/docker-compose
```
In order to update the local image, you can run the following commands:
```
docker pull linuxserver/docker-compose:"${DOCKER_COMPOSE_IMAGE_TAG:-latest}"
docker pull linuxserver/docker-compose:"${DOCKER_COMPOSE_IMAGE_TAG:-v2}"
docker image prune -f
```
To use the slimmer and more lightweight alpine based image, you can set an env var `DOCKER_COMPOSE_IMAGE_TAG=alpine` in your respective `.profile`. Alternatively you can set that var to a versioned image tag like `version-1.27.4` or `version-alpine-1.27.4` to pin it to a specific docker-compose version.
### Install Option 2:
We also publish binaries for docker-compose in [this repo](https://github.com/linuxserver/docker-docker-compose/releases). There are two versions, one for glibc based systems like Ubuntu and Debian, and one for musl based systems like Alpine. The latter are marked with the `alpine` tag. Each version contains binaries for `amd64`, `armhf` and `arm64`. You can pull these binaries into your system via the following commands to have a functional docker-compose install:
```
sudo curl -L --fail https://github.com/linuxserver/docker-docker-compose/releases/download/1.27.4-ls17/docker-compose-amd64 -o /usr/local/bin/docker-compose
sudo chmod +x /usr/local/bin/docker-compose
```
The above commands will use the v2 images (although invoked by`docker-compose` instead of `docker compose`). If you'd like to use v1 images, you can set an env var `DOCKER_COMPOSE_IMAGE_TAG=alpine`, `DOCKER_COMPOSE_IMAGE_TAG=ubuntu` in your respective `.profile`. Alternatively you can set that var to a versioned image tag like `v2-2.4.1-r1` or `version-alpine-1.27.4` to pin it to a specific docker-compose version.
## Single service Usage
Here's a basic example for deploying a Linuxserver container with docker-compose:
Here's a basic example for deploying a Linuxserver container with docker compose:
```yaml
version: "2.1"
@ -48,15 +63,15 @@ services:
restart: unless-stopped
```
If you save the above snippet in a file named `docker-compose.yml`, you can simply run `docker-compose up -d` from within the same folder and the heimdall image will be automatically pulled, and a container will be created and started. `up` means bring the services up, and `-d` means do it in the background.
If you save the above snippet in a file named `docker-compose.yml`, you can simply run `docker compose up -d` from within the same folder and the heimdall image will be automatically pulled, and a container will be created and started. `up` means bring the services up, and `-d` means do it in the background.
If you want to do it from a different folder or if you named the yaml file differently, ie. `heimdall.yml`, then you can define it in the command with `-f`: `docker-compose -f /path/to/heimdall.yml up -d`
If you want to do it from a different folder or if you named the yaml file differently, ie. `heimdall.yml`, then you can define it in the command with `-f`: `docker compose -f /path/to/heimdall.yml up -d`
To bring down the services, simply do `docker-compose down` or `docker-compose -f /path/to/heimdall.yml down` and all containers defined by the yml will be stopped and destroyed.
To bring down the services, simply do `docker compose down` or `docker compose -f /path/to/heimdall.yml down` and all containers defined by the yml will be stopped and destroyed.
## Multiple Service Usage
You can have multiple services managed by a single compose yaml. Copy the contents below the `services:` line in any of our readme yaml samples into the same yaml file and the `docker-compose up/down` commands will apply to all services at once.
You can have multiple services managed by a single compose yaml. Copy the contents below the `services:` line in any of our readme yaml samples into the same yaml file and the `docker compose up/down` commands will apply to all services at once.
Let's say you have the following in a yaml file named `docker-compose.yml`:
@ -104,27 +119,33 @@ services:
restart: unless-stopped
```
You now have 3 services defined in there: `heimdall`, `nginx` and `mariadb`. When you do a `docker-compose up -d`, it will first download the images for all three if they don't exist \(if they exist, they are not updated\) and it will create all three containers and start them. `docker-compose down` will bring all three services down and destroy the containers \(persistent data will remain\).
You now have 3 services defined in there: `heimdall`, `nginx` and `mariadb`. When you do a `docker compose up -d`, it will first download the images for all three if they don't exist \(if they exist, they are not updated\) and it will create all three containers and start them. `docker compose down` will bring all three services down and destroy the containers \(persistent data will remain\).
## Updates
If you want to update the images and recreate the containers with the same vars, it's extremely easy with docker-compose. First we tell it to update all images via `docker-compose pull`. Then we issue `docker-compose up -d` and it will automatically recreate the containers \(as necessary\) based on the updated images. If a container's image is already the latest and there was no update, it remains untouched.
If you want to update the images and recreate the containers with the same vars, it's extremely easy with docker-compose. First we tell it to update all images via `docker compose pull`. Then we issue `docker compose up -d` and it will automatically recreate the containers \(as necessary\) based on the updated images. If a container's image is already the latest and there was no update, it remains untouched.
Similarly, if you edit the contents of the yaml file and re-issue `docker-compose up -d`, only the containers affected by the changes to the yaml file will be recreated, others will be untouched.
Similarly, if you edit the contents of the yaml file and re-issue `docker compose up -d`, only the containers affected by the changes to the yaml file will be recreated, others will be untouched.
Defining the containers running on your server as code is a core tenet of a "Devops" approach to the world. Constructing elaborate `docker run` commands and then forgetting which variables you passed is a thing of the past when using `docker-compose`.
Defining the containers running on your server as code is a core tenet of a "Devops" approach to the world. Constructing elaborate `docker run` commands and then forgetting which variables you passed is a thing of the past when using `docker compose`.
## Support Requests
If you would like to request support, you can do so on [our forum](https://discourse.linuxserver.io/) or on [our discord server](https://discord.gg/YWrKVTn?target=_blank). When you do so, please provide all the necessary information like the server and platform info, docker container log and the compose yaml.
If your compose yaml makes use of `.env`, please post an output of `docker compose convert` or `docker compose convert -f /path/to/compose.yml` for the entire yaml, or `docker compose convert <service name>` for a single service, as it will automatically replace the environment variables with their actual values.
## Tips & Tricks
`docker-compose` expects a `docker-compose.yml` file in the current directory and if one isn't present it will complain. In order to improve your quality of life we suggest the use of bash aliases. The file path for the aliases below assumes that the `docker-compose.yml` file is being kept in the folder `/opt`. If your compose file is kept somewhere else, like in a home directory, then the path will need to be changed.
`docker compose` expects a `docker-compose.yml` file in the current directory and if one isn't present it will complain. In order to improve your quality of life we suggest the use of bash aliases. The file path for the aliases below assumes that the `docker-compose.yml` file is being kept in the folder `/opt`. If your compose file is kept somewhere else, like in a home directory, then the path will need to be changed.
Create or open the file `~/.bash_aliases` and populate with the following content:
```bash
alias dcup='docker-compose -f /opt/docker-compose.yml up -d' #brings up all containers if one is not defined after dcup
alias dcdown='docker-compose -f /opt/docker-compose.yml stop' #brings down all containers if one is not defined after dcdown
alias dcpull='docker-compose -f /opt/docker-compose.yml pull' #pulls all new images is specified after dcpull
alias dclogs='docker-compose -f /opt/docker-compose.yml logs -tf --tail="50" '
alias dcup='docker compose -f /opt/docker-compose.yml up -d' #brings up all containers if one is not defined after dcup
alias dcdown='docker compose -f /opt/docker-compose.yml stop' #brings down all containers if one is not defined after dcdown
alias dcpull='docker compose -f /opt/docker-compose.yml pull' #pulls all new images is specified after dcpull
alias dclogs='docker compose -f /opt/docker-compose.yml logs -tf --tail="50" '
alias dtail='docker logs -tf --tail="50" "$@"'
```
If the `docker-compose.yml` file is in a home directory, the following can be put in the `~/.bash_aliases` file.
@ -135,9 +156,9 @@ alias dcpull='docker-compose -f ~/docker-compose.yml pull' #pulls all new images
alias dclogs='docker-compose -f ~/docker-compose.yml logs -tf --tail="50" '
alias dtail='docker logs -tf --tail="50" "$@"'
```
There are multiple ways to see the logs of your containers. In some instances, using `docker logs` is preferable to `docker-compose logs`. By default `docker logs` will not run unless you define which service the logs are coming from. The `docker-compose logs` will pull all of the logs for the services defined in the `docker-compose.yml` file.
There are multiple ways to see the logs of your containers. In some instances, using `docker logs` is preferable to `docker compose logs`. By default `docker logs` will not run unless you define which service the logs are coming from. The `docker compose logs` will pull all of the logs for the services defined in the `docker-compose.yml` file.
When asking for help, you should post your logs or be ready to provide logs if someone requests it. If you are running multiple containers in your `docker-compose.yml` file, it is not helpful to submit **all** of the logs. If you are experiencing issues with a single service, say Heimdall, then you would want to get your logs using `docker logs heimdall` or `docker-compose logs heimdall`. The bash_alias for `dclogs` can be used if you define your service after you've typed the alias. Likewise, the bash_alias `detail` will not run without defining the service after it.
When asking for help, you should post your logs or be ready to provide logs if someone requests it. If you are running multiple containers in your `docker-compose.yml` file, it is not helpful to submit **all** of the logs. If you are experiencing issues with a single service, say Heimdall, then you would want to get your logs using `docker logs heimdall` or `docker compose logs heimdall`. The bash_alias for `dclogs` can be used if you define your service after you've typed the alias. Likewise, the bash_alias `detail` will not run without defining the service after it.
Some distributions, like Ubuntu, already have the code snippet below in the `~/.bashrc` file. If it is not included, you'll need to add the following to your `~/.bashrc` file in order for the aliases file to be picked up:

28
images/docker-adguardhome-sync.md
Wyświetl plik

@ -21,25 +21,25 @@ title: adguardhome-sync
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/adguardhome-sync` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/adguardhome-sync:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Version Tags
This image provides various versions that are available via tags. `latest` tag usually provides the latest stable version. Others are considered under development and caution must be exercised when using them.
This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.
| Tag | Description |
| :----: | --- |
| latest | Stable releases from GitHub |
| Tag | Available | Description |
| :----: | :----: |--- |
| latest | ✅ | Stable releases from GitHub |
## Application Setup
@ -56,7 +56,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
adguardhome-sync:
image: lscr.io/linuxserver/adguardhome-sync
image: lscr.io/linuxserver/adguardhome-sync:latest
container_name: adguardhome-sync
environment:
- PUID=1000
@ -82,7 +82,7 @@ docker run -d \
-p 8080:8080 \
-v /path/to/appdata/config:/config \
--restart unless-stopped \
lscr.io/linuxserver/adguardhome-sync
lscr.io/linuxserver/adguardhome-sync:latest
```
## Parameters
@ -160,7 +160,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' adguardhome-sync`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/adguardhome-sync`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/adguardhome-sync:latest`
## Versions

27
images/docker-airsonic-advanced.md
Wyświetl plik

@ -21,24 +21,25 @@ title: airsonic-advanced
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/airsonic-advanced` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/airsonic-advanced:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ❌ | |
## Version Tags
This image provides various versions that are available via tags. `latest` tag usually provides the latest stable version. Others are considered under development and caution must be exercised when using them.
This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.
| Tag | Description |
| :----: | --- |
| latest | Latest releases of Airsonic-Advanced |
| Tag | Available | Description |
| :----: | :----: |--- |
| latest | ✅ | Latest releases of Airsonic-Advanced |
## Application Setup
@ -65,7 +66,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
airsonic-advanced:
image: lscr.io/linuxserver/airsonic-advanced
image: lscr.io/linuxserver/airsonic-advanced:latest
container_name: airsonic-advanced
environment:
- PUID=1000
@ -104,7 +105,7 @@ docker run -d \
-v </path/to/other media>:/media `#optional` \
--device /dev/snd:/dev/snd `#optional` \
--restart unless-stopped \
lscr.io/linuxserver/airsonic-advanced
lscr.io/linuxserver/airsonic-advanced:latest
```
## Parameters
@ -193,7 +194,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' airsonic-advanced`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/airsonic-advanced`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/airsonic-advanced:latest`
## Versions

21
images/docker-apprise-api.md
Wyświetl plik

@ -27,17 +27,18 @@ Apprise API was designed to easily fit into existing (and new) eco-systems that
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/apprise-api` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/apprise-api:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Usage
@ -50,7 +51,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
apprise-api:
image: lscr.io/linuxserver/apprise-api
image: lscr.io/linuxserver/apprise-api:latest
container_name: apprise-api
environment:
- PUID=1000
@ -74,7 +75,7 @@ docker run -d \
-p 8000:8000 \
-v /path/to/config:/config \
--restart unless-stopped \
lscr.io/linuxserver/apprise-api
lscr.io/linuxserver/apprise-api:latest
```
## Parameters
@ -151,7 +152,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' apprise-api`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/apprise-api`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/apprise-api:latest`
## Versions

16
images/docker-audacity.md
Wyświetl plik

@ -23,13 +23,15 @@ title: audacity
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/audacity` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/audacity:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ❌ | |
| armhf| ❌ | |
## Application Setup
@ -52,7 +54,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
audacity:
image: lscr.io/linuxserver/audacity
image: lscr.io/linuxserver/audacity:latest
container_name: audacity
environment:
- PUID=1000
@ -76,7 +78,7 @@ docker run -d \
-p 3000:3000 \
-v /path/to/config:/config \
--restart unless-stopped \
lscr.io/linuxserver/audacity
lscr.io/linuxserver/audacity:latest
```
## Parameters
@ -153,7 +155,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' audacity`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/audacity`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/audacity:latest`
## Versions

24
images/docker-babybuddy.md
Wyświetl plik

@ -21,17 +21,17 @@ title: babybuddy
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/babybuddy` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/babybuddy:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -50,10 +50,11 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
babybuddy:
image: lscr.io/linuxserver/babybuddy
image: lscr.io/linuxserver/babybuddy:latest
container_name: babybuddy
environment:
- TZ=Europe/London
- CSRF_TRUSTED_ORIGINS=http://127.0.0.1:8000,https://babybuddy.domain.com
volumes:
- /path/to/appdata:/config
ports:
@ -67,10 +68,11 @@ services:
docker run -d \
--name=babybuddy \
-e TZ=Europe/London \
-e CSRF_TRUSTED_ORIGINS=http://127.0.0.1:8000,https://babybuddy.domain.com \
-p 8000:8000 \
-v /path/to/appdata:/config \
--restart unless-stopped \
lscr.io/linuxserver/babybuddy
lscr.io/linuxserver/babybuddy:latest
```
## Parameters
@ -88,6 +90,7 @@ Docker images are configured using parameters passed at runtime (such as those a
| Env | Function |
| :----: | --- |
| `TZ=Europe/London` | Specify a timezone to use EG Europe/London |
| `CSRF_TRUSTED_ORIGINS=http://127.0.0.1:8000,https://babybuddy.domain.com` | Add any address you'd like to access babybuddy at (comma separated, no spaces) |
### Volume Mappings (`-v`)
@ -132,10 +135,11 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' babybuddy`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/babybuddy`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/babybuddy:latest`
## Versions
* **03.04.22:** - Rebase to alpine-nginx baseimage. Add `CSRF_TRUSTED_ORIGINS` env var.
* **11.12.21:** - Add py3-mysqlclient for mysql/mariadb.
* **14.11.21:** - Add lxml dependencies (temp fix for amd64 by force compiling lxml).
* **25.07.21:** - Add libpq for postgresql.

30
images/docker-bazarr.md
Wyświetl plik

@ -21,26 +21,26 @@ title: bazarr
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/bazarr` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/bazarr:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Version Tags
This image provides various versions that are available via tags. `latest` tag usually provides the latest stable version. Others are considered under development and caution must be exercised when using them.
This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.
| Tag | Description |
| :----: | --- |
| latest | Stable releases from Bazarr |
| development | Pre-releases from Bazarr |
| Tag | Available | Description |
| :----: | :----: |--- |
| latest | ✅ | Stable releases from Bazarr |
| development | ✅ | Pre-releases from Bazarr |
## Application Setup
@ -58,7 +58,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
bazarr:
image: lscr.io/linuxserver/bazarr
image: lscr.io/linuxserver/bazarr:latest
container_name: bazarr
environment:
- PUID=1000
@ -86,7 +86,7 @@ docker run -d \
-v /path/to/movies:/movies `#optional` \
-v /path/to/tv:/tv `#optional` \
--restart unless-stopped \
lscr.io/linuxserver/bazarr
lscr.io/linuxserver/bazarr:latest
```
## Parameters
@ -165,7 +165,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' bazarr`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/bazarr`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/bazarr:latest`
## Versions

30
images/docker-beets.md
Wyświetl plik

@ -21,26 +21,26 @@ title: beets
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/beets` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/beets:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Version Tags
This image provides various versions that are available via tags. `latest` tag usually provides the latest stable version. Others are considered under development and caution must be exercised when using them.
This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.
| Tag | Description |
| :----: | --- |
| latest | Stable Beets Releases |
| nightly | Built against head of Beets git, generally considered unstable but a likely choice for power users of the application. |
| Tag | Available | Description |
| :----: | :----: |--- |
| latest | ✅ | Stable Beets Releases |
| nightly | ✅ | Built against head of Beets git, generally considered unstable but a likely choice for power users of the application. |
## Application Setup
@ -65,7 +65,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
beets:
image: lscr.io/linuxserver/beets
image: lscr.io/linuxserver/beets:latest
container_name: beets
environment:
- PUID=1000
@ -93,7 +93,7 @@ docker run -d \
-v </path/to/music/library>:/music \
-v </path/to/ingest>:/downloads \
--restart unless-stopped \
lscr.io/linuxserver/beets
lscr.io/linuxserver/beets:latest
```
## Parameters
@ -172,7 +172,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' beets`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/beets`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/beets:latest`
## Versions

23
images/docker-blender.md
Wyświetl plik

@ -21,17 +21,17 @@ title: blender
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/blender` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/blender:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -67,6 +67,8 @@ We automatically add the necessary environment variable that will utilise all th
Arm devices can run this image, but generally should not mount in /dev/dri. The OpenGL ES version is not high enough to run Blender. The program can run on these platforms though, leveraging CPU LLVMPipe rendering.
Due to lack of arm32/64 binaries from the upstream project, our arm32/64 images install the latest version from the ubuntu repo, which is usually behind and thus the version the image is tagged with does not match the version contained.
#### Keyboard Layouts
This should match the layout on the computer you are accessing the container from.
@ -96,7 +98,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
blender:
image: lscr.io/linuxserver/blender
image: lscr.io/linuxserver/blender:latest
container_name: blender
security_opt:
- seccomp:unconfined #optional
@ -130,7 +132,7 @@ docker run -d \
-v /path/to/config:/config \
--device /dev/dri:/dev/dri `#optional` \
--restart unless-stopped \
lscr.io/linuxserver/blender
lscr.io/linuxserver/blender:latest
```
## Parameters
@ -216,8 +218,9 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' blender`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/blender`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/blender:latest`
## Versions
* **06.05.22:** - Use the full semver version in image tags. Arm32/64 version tags are inaccurate due to installing from ubuntu repo, which is usually behind.
* **12.03.22:** - Initial Release.

20
images/docker-boinc.md
Wyświetl plik

@ -21,17 +21,17 @@ title: boinc
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/boinc` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/boinc:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -70,7 +70,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
boinc:
image: lscr.io/linuxserver/boinc
image: lscr.io/linuxserver/boinc:latest
container_name: boinc
environment:
- PUID=1000
@ -99,7 +99,7 @@ docker run -d \
-v /path/to/data:/config \
--device /dev/dri:/dev/dri `#optional` \
--restart unless-stopped \
lscr.io/linuxserver/boinc
lscr.io/linuxserver/boinc:latest
```
## Parameters
@ -183,7 +183,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' boinc`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/boinc`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/boinc:latest`
## Versions

34
images/docker-booksonic-air.md
Wyświetl plik

@ -17,30 +17,31 @@ title: booksonic-air
[![Jenkins Build](https://img.shields.io/jenkins/build?labelColor=555555&logoColor=ffffff&style=for-the-badge&jobUrl=https%3A%2F%2Fci.linuxserver.io%2Fjob%2FDocker-Pipeline-Builders%2Fjob%2Fdocker-booksonic-air%2Fjob%2Fmaster%2F&logo=jenkins)](https://ci.linuxserver.io/job/Docker-Pipeline-Builders/job/docker-booksonic-air/job/master/)
[![LSIO CI](https://img.shields.io/badge/dynamic/yaml?color=94398d&labelColor=555555&logoColor=ffffff&style=for-the-badge&label=CI&query=CI&url=https%3A%2F%2Fci-tests.linuxserver.io%2Flinuxserver%2Fbooksonic-air%2Flatest%2Fci-status.yml)](https://ci-tests.linuxserver.io/linuxserver/booksonic-air/latest/index.html)
[Booksonic-air](http://booksonic.org) is a platform for accessing the audiobooks you own wherever you are. At the moment the platform consists of
Booksonic Air - A server for streaming your audiobooks, successor to the original Booksonic server and based on Airsonic. Booksonic App - An DSub based Android app for connection to Booksonic-Air servers. .
[Booksonic-air](http://booksonic.org) is a platform for accessing the audiobooks you own wherever you are. At the moment the platform consists of:
* Booksonic Air - A server for streaming your audiobooks, successor to the original Booksonic server and based on Airsonic.
* Booksonic App - An DSub based Android app for connection to Booksonic-Air servers.
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/booksonic-air` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/booksonic-air:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Version Tags
This image provides various versions that are available via tags. `latest` tag usually provides the latest stable version. Others are considered under development and caution must be exercised when using them.
This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.
| Tag | Description |
| :----: | --- |
| latest | Stable booksonic-air releases |
| Tag | Available | Description |
| :----: | :----: |--- |
| latest | ✅ | Stable booksonic-air releases |
## Application Setup
@ -57,7 +58,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
booksonic-air:
image: lscr.io/linuxserver/booksonic-air
image: lscr.io/linuxserver/booksonic-air:latest
container_name: booksonic-air
environment:
- PUID=1000
@ -89,7 +90,7 @@ docker run -d \
-v </path/to/podcasts>:/podcasts \
-v </path/to/othermedia>:/othermedia \
--restart unless-stopped \
lscr.io/linuxserver/booksonic-air
lscr.io/linuxserver/booksonic-air:latest
```
## Parameters
@ -170,8 +171,9 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' booksonic-air`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/booksonic-air`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/booksonic-air:latest`
## Versions
* **18.04.22:** - Rebase to Alpine 3.15.
* **15.09.20:** - Initial Release.

18
images/docker-bookstack.md
Wyświetl plik

@ -25,17 +25,17 @@ For more information on BookStack visit their website and check it out: https://
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/bookstack` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/bookstack:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -118,7 +118,7 @@ docker run -d \
-p 6875:80 \
-v /path/to/data:/config \
--restart unless-stopped \
lscr.io/linuxserver/bookstack
lscr.io/linuxserver/bookstack:latest
```
## Parameters
@ -199,7 +199,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' bookstack`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/bookstack`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/bookstack:latest`
## Versions

21
images/docker-budge.md
Wyświetl plik

@ -21,17 +21,17 @@ title: budge
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/budge` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/budge:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -48,7 +48,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
budge:
image: lscr.io/linuxserver/budge
image: lscr.io/linuxserver/budge:latest
container_name: budge
environment:
- PUID=1000
@ -74,7 +74,7 @@ docker run -d \
-p 443:443 \
-v /path/to/budge/config:/config \
--restart unless-stopped \
lscr.io/linuxserver/budge
lscr.io/linuxserver/budge:latest
```
## Parameters
@ -152,8 +152,9 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' budge`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/budge`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/budge:latest`
## Versions
* **04.15.22:** - Added NPM command to run db migrations.
* **02.05.22:** - Initial Release.

32
images/docker-calibre-web.md
Wyświetl plik

@ -23,26 +23,26 @@ This software is a fork of library and licensed under the GPL v3 License.
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/calibre-web` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/calibre-web:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Version Tags
This image provides various versions that are available via tags. `latest` tag usually provides the latest stable version. Others are considered under development and caution must be exercised when using them.
This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.
| Tag | Description |
| :----: | --- |
| latest | Releases of Calibre-Web |
| nightly | Commits to the master branch of Calibre-Web |
| Tag | Available | Description |
| :----: | :----: |--- |
| latest | ✅ | Releases of Calibre-Web |
| nightly | ✅ | Commits to the master branch of Calibre-Web |
## Application Setup
@ -58,7 +58,7 @@ Unrar is included by default and needs to be set in the Calibre-Web admin page (
**x86-64 only** We have implemented the optional ability to pull in the dependencies to enable ebook conversion utilising Calibre, this means if you don't require this feature the container isn't uneccessarily bloated but should you require it, it is easily available.
This optional layer will be rebuilt automatically on our CI pipeline upon new Calibre releases so you can stay up to date.
To use this option add the optional environmental variable as detailed above to pull an addition docker layer to enable ebook conversion and then in the Calibre-Web admin page (Basic Configuration:External Binaries) set the **Path to Calibre E-Book Converter** to `/usr/bin/ebook-convert`
To use this option add the optional environmental variable as shown below to pull an addition docker layer to enable ebook conversion and then in the Calibre-Web admin page (Basic Configuration:External Binaries) set the **Path to Calibre E-Book Converter** to `/usr/bin/ebook-convert`
This image contains the [kepubify](https://pgaskin.net/kepubify/) ebook conversion tool (MIT License) to convert epub to kepub. In the Calibre-Web admin page (Basic Configuration:External Binaries) set the **Path to Kepubify E-Book Converter** to `/usr/bin/kepubify`
@ -84,7 +84,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
calibre-web:
image: lscr.io/linuxserver/calibre-web
image: lscr.io/linuxserver/calibre-web:latest
container_name: calibre-web
environment:
- PUID=1000
@ -114,7 +114,7 @@ docker run -d \
-v /path/to/data:/config \
-v /path/to/calibre/library:/books \
--restart unless-stopped \
lscr.io/linuxserver/calibre-web
lscr.io/linuxserver/calibre-web:latest
```
## Parameters
@ -194,7 +194,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' calibre-web`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/calibre-web`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/calibre-web:latest`
## Versions

31
images/docker-calibre.md
Wyświetl plik

@ -21,26 +21,26 @@ title: calibre
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/calibre` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/calibre:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | latest |
| arm64 | arm64v8-arch |
| armhf | arm32v7-arch |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Version Tags
This image provides various versions that are available via tags. `latest` tag usually provides the latest stable version. Others are considered under development and caution must be exercised when using them.
This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.
| Tag | Description |
| :----: | --- |
| latest | Default Ubuntu based image |
| arch | Arch based image supporting arm platforms |
| Tag | Available | Description |
| :----: | :----: |--- |
| latest | ✅ | Default Ubuntu based image |
| arch | ✅ | Arch based image supporting arm platforms |
## Application Setup
@ -63,7 +63,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
calibre:
image: lscr.io/linuxserver/calibre
image: lscr.io/linuxserver/calibre:latest
container_name: calibre
environment:
- PUID=1000
@ -93,7 +93,7 @@ docker run -d \
-p 8081:8081 \
-v /path/to/data:/config \
--restart unless-stopped \
lscr.io/linuxserver/calibre
lscr.io/linuxserver/calibre:latest
```
## Parameters
@ -173,10 +173,11 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' calibre`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/calibre`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/calibre:latest`
## Versions
* **31.03.22:** - Fix umask.
* **28.02.22:** - Add speech support to bionic image.
* **05.01.22:** - Add arch branch for arm platforms.
* **20.04.21:** - Fix the HOME folder.

18
images/docker-chevereto.md
Wyświetl plik

@ -21,17 +21,17 @@ title: chevereto
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/chevereto` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/chevereto:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -102,7 +102,7 @@ docker run -d \
-v <path to config on host>:/config \
-v <path to data on host>:/data \
--restart unless-stopped \
lscr.io/linuxserver/chevereto
lscr.io/linuxserver/chevereto:latest
```
## Parameters
@ -181,7 +181,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' chevereto`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/chevereto`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/chevereto:latest`
## Versions

36
images/docker-cloud9.md
Wyświetl plik

@ -21,29 +21,29 @@ title: cloud9
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/cloud9` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/cloud9:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Version Tags
This image provides various versions that are available via tags. `latest` tag usually provides the latest stable version. Others are considered under development and caution must be exercised when using them.
This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.
| Tag | Description |
| :----: | --- |
| latest | Docker and Compose environment pre-installed |
| go | Basic Golang environment pre-installed |
| nodejs | Current stable NodeJS/NPM environment pre-installed |
| python | Current Python3 environment pre-installed |
| ruby | Current Ruby environment pre-installed |
| Tag | Available | Description |
| :----: | :----: |--- |
| latest | ✅ | Docker and Compose environment pre-installed |
| go | ✅ | Basic Golang environment pre-installed |
| nodejs | ✅ | Current stable NodeJS/NPM environment pre-installed |
| python | ✅ | Current Python3 environment pre-installed |
| ruby | ✅ | Current Ruby environment pre-installed |
## Application Setup
@ -60,7 +60,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
cloud9:
image: lscr.io/linuxserver/cloud9
image: lscr.io/linuxserver/cloud9:latest
container_name: cloud9
environment:
- PUID=1000
@ -92,7 +92,7 @@ docker run -d \
-v /path/to/your/code:/code `#optional` \
-v /var/run/docker.sock:/var/run/docker.sock `#optional` \
--restart unless-stopped \
lscr.io/linuxserver/cloud9
lscr.io/linuxserver/cloud9:latest
```
## Parameters
@ -173,7 +173,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' cloud9`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/cloud9`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/cloud9:latest`
## Versions

32
images/docker-code-server.md
Wyświetl plik

@ -27,27 +27,27 @@ title: code-server
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/code-server` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/code-server:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Version Tags
This image provides various versions that are available via tags. `latest` tag usually provides the latest stable version. Others are considered under development and caution must be exercised when using them.
This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.
| Tag | Description |
| :----: | --- |
| latest | Stable releases |
| focal | DEPRECATED (no longer updated, `latest` is rebased on focal) - Stable releases, based on Ubuntu Focal |
| development | DEPRECATED (no longer updated) - Prereleases from their GitHub |
| Tag | Available | Description |
| :----: | :----: |--- |
| latest | ✅ | Stable releases |
| focal | ✅ | DEPRECATED (no longer updated, `latest` is rebased on focal) - Stable releases, based on Ubuntu Focal |
| development | ✅ | DEPRECATED (no longer updated) - Prereleases from their GitHub |
## Application Setup
@ -75,7 +75,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
code-server:
image: lscr.io/linuxserver/code-server
image: lscr.io/linuxserver/code-server:latest
container_name: code-server
environment:
- PUID=1000
@ -111,7 +111,7 @@ docker run -d \
-p 8443:8443 \
-v /path/to/appdata/config:/config \
--restart unless-stopped \
lscr.io/linuxserver/code-server
lscr.io/linuxserver/code-server:latest
```
## Parameters
@ -194,7 +194,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' code-server`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/code-server`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/code-server:latest`
## Versions

20
images/docker-cops.md
Wyświetl plik

@ -52,17 +52,17 @@ If you want to use the OPDS feed don't forget to specify feed.php at the end of
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/cops` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/cops:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -79,7 +79,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
cops:
image: lscr.io/linuxserver/cops
image: lscr.io/linuxserver/cops:latest
container_name: cops
environment:
- PUID=1000
@ -105,7 +105,7 @@ docker run -d \
-v <path to data>:/config \
-v <path to data>:/books \
--restart unless-stopped \
lscr.io/linuxserver/cops
lscr.io/linuxserver/cops:latest
```
## Parameters
@ -183,7 +183,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' cops`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/cops`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/cops:latest`
## Versions

20
images/docker-daapd.md
Wyświetl plik

@ -21,17 +21,17 @@ title: daapd
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/daapd` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/daapd:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -64,7 +64,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
daapd:
image: lscr.io/linuxserver/daapd
image: lscr.io/linuxserver/daapd:latest
container_name: daapd
network_mode: host
environment:
@ -89,7 +89,7 @@ docker run -d \
-v <path to data>:/config \
-v <path to music>:/music \
--restart unless-stopped \
lscr.io/linuxserver/daapd
lscr.io/linuxserver/daapd:latest
```
## Parameters
@ -172,7 +172,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' daapd`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/daapd`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/daapd:latest`
## Versions

19
images/docker-darktable.md
Wyświetl plik

@ -21,16 +21,17 @@ title: darktable
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/darktable` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/darktable:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | latest |
| arm64 | arm64v8-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ❌ | |
## Application Setup
@ -53,7 +54,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
darktable:
image: lscr.io/linuxserver/darktable
image: lscr.io/linuxserver/darktable:latest
container_name: darktable
environment:
- PUID=1000
@ -77,7 +78,7 @@ docker run -d \
-p 3000:3000 \
-v /path/to/config:/config \
--restart unless-stopped \
lscr.io/linuxserver/darktable
lscr.io/linuxserver/darktable:latest
```
## Parameters
@ -154,7 +155,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' darktable`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/darktable`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/darktable:latest`
## Versions

20
images/docker-davos.md
Wyświetl plik

@ -21,17 +21,17 @@ title: davos
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/davos` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/davos:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -48,7 +48,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
davos:
image: lscr.io/linuxserver/davos
image: lscr.io/linuxserver/davos:latest
container_name: davos
environment:
- PUID=1000
@ -72,7 +72,7 @@ docker run -d \
-v <path to data>:/config \
-v <path to downloads folder>:/download \
--restart unless-stopped \
lscr.io/linuxserver/davos
lscr.io/linuxserver/davos:latest
```
## Parameters
@ -149,7 +149,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' davos`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/davos`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/davos:latest`
## Versions

20
images/docker-ddclient.md
Wyświetl plik

@ -21,17 +21,17 @@ title: ddclient
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/ddclient` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/ddclient:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -54,7 +54,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
ddclient:
image: lscr.io/linuxserver/ddclient
image: lscr.io/linuxserver/ddclient:latest
container_name: ddclient
environment:
- PUID=1000
@ -75,7 +75,7 @@ docker run -d \
-e TZ=Europe/London \
-v <path to data>:/config \
--restart unless-stopped \
lscr.io/linuxserver/ddclient
lscr.io/linuxserver/ddclient:latest
```
## Parameters
@ -151,7 +151,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' ddclient`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/ddclient`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/ddclient:latest`
## Versions

20
images/docker-deluge.md
Wyświetl plik

@ -26,17 +26,17 @@ title: deluge
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/deluge` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/deluge:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -57,7 +57,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
deluge:
image: lscr.io/linuxserver/deluge
image: lscr.io/linuxserver/deluge:latest
container_name: deluge
environment:
- PUID=1000
@ -89,7 +89,7 @@ docker run -d \
-v /path/to/deluge/config:/config \
-v /path/to/your/downloads:/downloads \
--restart unless-stopped \
lscr.io/linuxserver/deluge
lscr.io/linuxserver/deluge:latest
```
## Parameters
@ -170,7 +170,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' deluge`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/deluge`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/deluge:latest`
## Versions

20
images/docker-digikam.md
Wyświetl plik

@ -21,17 +21,17 @@ title: digikam
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/digikam` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/digikam:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -78,7 +78,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
digikam:
image: lscr.io/linuxserver/digikam
image: lscr.io/linuxserver/digikam:latest
container_name: digikam
network_mode: host
environment:
@ -108,7 +108,7 @@ docker run -d \
-p 3000:3000 `#optional` \
-v /path/to/config:/config \
--restart unless-stopped \
lscr.io/linuxserver/digikam
lscr.io/linuxserver/digikam:latest
```
## Parameters
@ -193,7 +193,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' digikam`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/digikam`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/digikam:latest`
## Versions

21
images/docker-dillinger.md
Wyświetl plik

@ -21,17 +21,17 @@ title: dillinger
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/dillinger` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/dillinger:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ❌ | |
## Application Setup
@ -48,7 +48,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
dillinger:
image: lscr.io/linuxserver/dillinger
image: lscr.io/linuxserver/dillinger:latest
container_name: dillinger
environment:
- PUID=1000
@ -72,7 +72,7 @@ docker run -d \
-p 8080:8080 \
-v <path to configs>:/config \
--restart unless-stopped \
lscr.io/linuxserver/dillinger
lscr.io/linuxserver/dillinger:latest
```
## Parameters
@ -149,8 +149,9 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' dillinger`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/dillinger`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/dillinger:latest`
## Versions
* **19.04.22:** - Rebase to Alpine.
* **31.05.19:** - Initial Release.

18
images/docker-diskover.md
Wyświetl plik

@ -21,17 +21,17 @@ title: diskover
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/diskover` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/diskover:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -117,7 +117,7 @@ docker run -d \
-v /path/to/diskover/config:/config \
-v /path/to/diskover/data:/data \
--restart unless-stopped \
lscr.io/linuxserver/diskover
lscr.io/linuxserver/diskover:latest
```
## Parameters
@ -199,7 +199,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' diskover`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/diskover`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/diskover:latest`
## Versions

4
images/docker-docker-compose.md
Wyświetl plik

@ -42,9 +42,9 @@ Find us at:
[![Docker Stars](https://img.shields.io/docker/stars/linuxserver/docker-compose.svg?color=94398d&labelColor=555555&logoColor=ffffff&style=for-the-badge&label=stars&logo=docker)](https://hub.docker.com/r/linuxserver/docker-compose)
[![Jenkins Build](https://img.shields.io/jenkins/build?labelColor=555555&logoColor=ffffff&style=for-the-badge&jobUrl=https%3A%2F%2Fci.linuxserver.io%2Fjob%2FDocker-Pipeline-Builders%2Fjob%2Fdocker-docker-compose%2Fjob%2Fmaster%2F&logo=jenkins)](https://ci.linuxserver.io/job/Docker-Pipeline-Builders/job/docker-docker-compose/job/master/)
[docker-compose](https://github.com/docker-compose/docker-compose) is a tool for defining and running multi-container Docker applications. With Compose, you use a Compose file to configure your application's services. Then, using a single command, you create and start all the services from your configuration.
[docker-compose](https://github.com/docker/compose) is a tool for defining and running multi-container Docker applications. With Compose, you use a Compose file to configure your application's services. Then, using a single command, you create and start all the services from your configuration.
[![docker-compose](https://github.com/docker/compose/raw/master/logo.png)](https://github.com/docker-compose/docker-compose)
[![docker-compose](https://github.com/docker/compose/raw/master/logo.png)](https://github.com/docker/compose)
## Supported Architectures

20
images/docker-dokuwiki.md
Wyświetl plik

@ -21,17 +21,17 @@ title: dokuwiki
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/dokuwiki` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/dokuwiki:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -48,7 +48,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
dokuwiki:
image: lscr.io/linuxserver/dokuwiki
image: lscr.io/linuxserver/dokuwiki:latest
container_name: dokuwiki
environment:
- PUID=1000
@ -74,7 +74,7 @@ docker run -d \
-p 443:443 `#optional` \
-v /path/to/appdata/config:/config \
--restart unless-stopped \
lscr.io/linuxserver/dokuwiki
lscr.io/linuxserver/dokuwiki:latest
```
## Parameters
@ -152,7 +152,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' dokuwiki`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/dokuwiki`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/dokuwiki:latest`
## Versions

36
images/docker-domoticz.md
Wyświetl plik

@ -21,29 +21,29 @@ title: domoticz
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/domoticz` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/domoticz:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Version Tags
This image provides various versions that are available via tags. `latest` tag usually provides the latest stable version. Others are considered under development and caution must be exercised when using them.
This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.
| Tag | Description |
| :----: | --- |
| latest | Current latest stable. |
| stable | Old stable version. Please change to latest branch for stable releases. |
| stable-4.9700 | Old stable version. Will not be updated anymore! |
| stable-3.815 | Old stable version. Will not be updated anymore! |
| stable-3.5877 | Old stable version. Will not be updated anymore! |
| Tag | Available | Description |
| :----: | :----: |--- |
| latest | ✅ | Current latest stable. |
| stable | ✅ | Old stable version. Please change to latest branch for stable releases. |
| stable-4.9700 | ✅ | Old stable version. Will not be updated anymore! |
| stable-3.815 | ✅ | Old stable version. Will not be updated anymore! |
| stable-3.5877 | ✅ | Old stable version. Will not be updated anymore! |
## Application Setup
@ -61,7 +61,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
domoticz:
image: lscr.io/linuxserver/domoticz
image: lscr.io/linuxserver/domoticz:latest
container_name: domoticz
environment:
- PUID=1000
@ -96,7 +96,7 @@ docker run -d \
-v <path to data>:/config \
--device path to device:path to device \
--restart unless-stopped \
lscr.io/linuxserver/domoticz
lscr.io/linuxserver/domoticz:latest
```
### Passing Through USB Devices
@ -195,7 +195,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' domoticz`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/domoticz`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/domoticz:latest`
## Versions

31
images/docker-doplarr.md
Wyświetl plik

@ -21,16 +21,17 @@ title: doplarr
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/doplarr` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/doplarr:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ❌ | |
## Application Setup
@ -56,7 +57,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
doplarr:
image: lscr.io/linuxserver/doplarr
image: lscr.io/linuxserver/doplarr:latest
container_name: doplarr
environment:
- PUID=1000
@ -70,10 +71,11 @@ services:
- SONARR__API=<sonarr__api>
- SONARR__URL=http://localhost:8989
- DISCORD__MAX_RESULTS=25 #optional
- DISCORD__ROLE_ID=<not_set_by_default> #optional
- DISCORD__REQUESTED_MSG_STYLE=:plain #optional
- SONARR__QUALITY_PROFILE=<not_set_by_default> #optional
- RADARR__QUALITY_PROFILE=<not_set_by_default> #optional
- SONARR__ROOTFOLDER=<not_set_by_default> #optional
- RADARR__ROOTFOLDER=<not_set_by_default> #optional
- SONARR__LANGUAGE_PROFILE=<not_set_by_default> #optional
- OVERSEERR__DEFAULT_ID=<not_set_by_default> #optional
- PARTIAL_SEASONS=true #optional
@ -100,10 +102,11 @@ docker run -d \
-e SONARR__API=<sonarr__api> \
-e SONARR__URL=http://localhost:8989 \
-e DISCORD__MAX_RESULTS=25 `#optional` \
-e DISCORD__ROLE_ID=<not_set_by_default> `#optional` \
-e DISCORD__REQUESTED_MSG_STYLE=:plain `#optional` \
-e SONARR__QUALITY_PROFILE=<not_set_by_default> `#optional` \
-e RADARR__QUALITY_PROFILE=<not_set_by_default> `#optional` \
-e SONARR__ROOTFOLDER=<not_set_by_default> `#optional` \
-e RADARR__ROOTFOLDER=<not_set_by_default> `#optional` \
-e SONARR__LANGUAGE_PROFILE=<not_set_by_default> `#optional` \
-e OVERSEERR__DEFAULT_ID=<not_set_by_default> `#optional` \
-e PARTIAL_SEASONS=true `#optional` \
@ -111,7 +114,7 @@ docker run -d \
-e JAVA_OPTS=<not_set_by_default> `#optional` \
-v </path/to/appdata/config>:/config \
--restart unless-stopped \
lscr.io/linuxserver/doplarr
lscr.io/linuxserver/doplarr:latest
```
## Parameters
@ -138,11 +141,12 @@ Docker images are configured using parameters passed at runtime (such as those a
| `SONARR__API=<sonarr__api>` | Specify your Sonarr API key. Leave blank if using Overseerr. |
| `SONARR__URL=http://localhost:8989` | Specify your Sonarr URL. Leave blank if using Overseerr. |
| `DISCORD__MAX_RESULTS=25` | Sets the maximum size of the search results selection |
| `DISCORD__ROLE_ID=<not_set_by_default>` | The discord role id for users of the bot (omitting this lets everyone on the server use the bot) |
| `DISCORD__REQUESTED_MSG_STYLE=:plain` | Sets the style of the request alert message. One of `:plain` `:embed` `:none` |
| `SONARR__QUALITY_PROFILE=<not_set_by_default>` | The name of the quality profile to use by default for Sonarr |
| `RADARR__QUALITY_PROFILE=<not_set_by_default>` | The name of the quality profile to use by default for Radarr |
| `SONARR__LANGUAGE_PROFILE=<not_set_by_default>` | The name of the language profile to use by default for Radarr |
| `SONARR__ROOTFOLDER=<not_set_by_default>` | The root folder to use by default for Sonarr |
| `RADARR__ROOTFOLDER=<not_set_by_default>` | The root folder to use by default for Radarr |
| `SONARR__LANGUAGE_PROFILE=<not_set_by_default>` | The name of the language profile to use by default for Sonarr |
| `OVERSEERR__DEFAULT_ID=<not_set_by_default>` | The Overseerr user id to use by default if there is no associated discord account for the requester |
| `PARTIAL_SEASONS=true` | Sets whether users can request partial seasons. |
| `LOG_LEVEL=:info` | The log level for the logging backend. This can be changed for debugging purposes. One of trace `:debug` `:info` `:warn` `:error` `:fatal` `:report` |
@ -204,9 +208,10 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' doplarr`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/doplarr`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/doplarr:latest`
## Versions
* **01.05.22:** - Remove `DISCORD__ROLE_ID` environment variable, see [Permissions Configuration](https://github.com/kiranshila/Doplarr/blob/main/docs/configuration.md#permissions).
* **30.01.22:** - Variable adjustments.
* **30.01.22:** - Initial Release.

20
images/docker-doublecommander.md
Wyświetl plik

@ -21,17 +21,17 @@ title: doublecommander
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/doublecommander` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/doublecommander:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -54,7 +54,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
doublecommander:
image: lscr.io/linuxserver/doublecommander
image: lscr.io/linuxserver/doublecommander:latest
container_name: doublecommander
environment:
- PUID=1000
@ -80,7 +80,7 @@ docker run -d \
-v /path/to/config:/config \
-v /path/to/data:/data \
--restart unless-stopped \
lscr.io/linuxserver/doublecommander
lscr.io/linuxserver/doublecommander:latest
```
## Parameters
@ -158,7 +158,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' doublecommander`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/doublecommander`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/doublecommander:latest`
## Versions

24
images/docker-duckdns.md
Wyświetl plik

@ -21,23 +21,23 @@ title: duckdns
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/duckdns` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/duckdns:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
- Go to the [duckdns website](https://duckdns.org/), register your subdomain(s) and retrieve your token
- Create a container with your subdomain(s) and token
- It will update your IP with the DuckDNS service every 5 minutes
- It will update your IP with the DuckDNS service every 5 minutes (with a random jitter)
## Usage
@ -50,7 +50,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
duckdns:
image: lscr.io/linuxserver/duckdns
image: lscr.io/linuxserver/duckdns:latest
container_name: duckdns
environment:
- PUID=1000 #optional
@ -77,7 +77,7 @@ docker run -d \
-e LOG_FILE=false `#optional` \
-v /path/to/appdata/config:/config `#optional` \
--restart unless-stopped \
lscr.io/linuxserver/duckdns
lscr.io/linuxserver/duckdns:latest
```
## Parameters
@ -156,10 +156,12 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' duckdns`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/duckdns`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/duckdns:latest`
## Versions
* **17.05.22:** - Don't allow insecure connections and add timeout.
* **17.05.22:** - Add random jitter to update time.
* **23.02.22:** - Append to log file instead of overwriting every time.
* **03.05.21:** - Re-adjust cron timings to prevent peak times, update code formatting.
* **23.01.21:** - Rebasing to alpine 3.13.

31
images/docker-duplicati.md
Wyświetl plik

@ -21,26 +21,26 @@ title: duplicati
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/duplicati` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/duplicati:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Version Tags
This image provides various versions that are available via tags. `latest` tag usually provides the latest stable version. Others are considered under development and caution must be exercised when using them.
This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.
| Tag | Description |
| :----: | --- |
| latest | Beta releases of Duplicati |
| development | Canary releases of Duplicati |
| Tag | Available | Description |
| :----: | :----: |--- |
| latest | ✅ | Beta releases of Duplicati |
| development | ✅ | Canary releases of Duplicati |
## Application Setup
@ -57,7 +57,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
duplicati:
image: lscr.io/linuxserver/duplicati
image: lscr.io/linuxserver/duplicati:latest
container_name: duplicati
environment:
- PUID=1000
@ -87,7 +87,7 @@ docker run -d \
-v </path/to/backups>:/backups \
-v </path/to/source>:/source \
--restart unless-stopped \
lscr.io/linuxserver/duplicati
lscr.io/linuxserver/duplicati:latest
```
## Parameters
@ -167,10 +167,11 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' duplicati`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/duplicati`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/duplicati:latest`
## Versions
* **25.04.22:** - Rebase to mono:focal.
* **01.08.19:** - Rebase to Linuxserver LTS mono version.
* **16.07.19:** - Allow for additional command line arguments in an environment variable.
* **28.06.19:** - Rebase to bionic.

30
images/docker-emby.md
Wyświetl plik

@ -21,26 +21,26 @@ title: emby
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/emby` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/emby:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Version Tags
This image provides various versions that are available via tags. `latest` tag usually provides the latest stable version. Others are considered under development and caution must be exercised when using them.
This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.
| Tag | Description |
| :----: | --- |
| latest | Stable emby releases |
| beta | Beta emby releases |
| Tag | Available | Description |
| :----: | :----: |--- |
| latest | ✅ | Stable emby releases |
| beta | ✅ | Beta emby releases |
## Application Setup
@ -88,7 +88,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
emby:
image: lscr.io/linuxserver/emby
image: lscr.io/linuxserver/emby:latest
container_name: emby
environment:
- PUID=1000
@ -131,7 +131,7 @@ docker run -d \
--device /dev/video11:/dev/video11 `#optional` \
--device /dev/video12:/dev/video12 `#optional` \
--restart unless-stopped \
lscr.io/linuxserver/emby
lscr.io/linuxserver/emby:latest
```
## Parameters
@ -222,7 +222,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' emby`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/emby`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/emby:latest`
## Versions

20
images/docker-embystat.md
Wyświetl plik

@ -21,17 +21,17 @@ title: embystat
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/embystat` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/embystat:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -48,7 +48,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
embystat:
image: lscr.io/linuxserver/embystat
image: lscr.io/linuxserver/embystat:latest
container_name: embystat
environment:
- PUID=1000
@ -72,7 +72,7 @@ docker run -d \
-p 6555:6555 \
-v /path/to/appdata/config:/config \
--restart unless-stopped \
lscr.io/linuxserver/embystat
lscr.io/linuxserver/embystat:latest
```
## Parameters
@ -149,7 +149,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' embystat`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/embystat`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/embystat:latest`
## Versions

21
images/docker-emulatorjs.md
Wyświetl plik

@ -21,17 +21,17 @@ title: emulatorjs
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/emulatorjs` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/emulatorjs:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -97,7 +97,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
emulatorjs:
image: lscr.io/linuxserver/emulatorjs
image: lscr.io/linuxserver/emulatorjs:latest
container_name: emulatorjs
environment:
- PUID=1000
@ -129,7 +129,7 @@ docker run -d \
-v /path/to/config:/config \
-v /path/to/data:/data \
--restart unless-stopped \
lscr.io/linuxserver/emulatorjs
lscr.io/linuxserver/emulatorjs:latest
```
## Parameters
@ -210,10 +210,11 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' emulatorjs`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/emulatorjs`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/emulatorjs:latest`
## Versions
* **04.04.22:** - Ingest pre-built chdman bins during build time.
* **23.02.22:** - Update ingestion point for emulatorjs bins.
* **25.01.22:** - Allow users to mount in existing rom directories.
* **14.01.22:** - Add profile paths and rebase to Alpine 3.15.

21
images/docker-endlessh.md
Wyświetl plik

@ -21,17 +21,17 @@ title: endlessh
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/endlessh` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/endlessh:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -48,7 +48,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
endlessh:
image: lscr.io/linuxserver/endlessh
image: lscr.io/linuxserver/endlessh:latest
container_name: endlessh
environment:
- PUID=1000
@ -82,7 +82,7 @@ docker run -d \
-p 22:2222 \
-v /path/to/appdata:/config `#optional` \
--restart unless-stopped \
lscr.io/linuxserver/endlessh
lscr.io/linuxserver/endlessh:latest
```
## Parameters
@ -164,10 +164,11 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' endlessh`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/endlessh`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/endlessh:latest`
## Versions
* **16.04.22:** - Rebase to Alpine 3.15.
* **07.10.21:** - Fix typo on MAXLINES var.
* **08.06.21:** - Add BINDFAMILY option.
* **16.04.21:** - Initial Release.

20
images/docker-filezilla.md
Wyświetl plik

@ -21,17 +21,17 @@ title: filezilla
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/filezilla` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/filezilla:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -54,7 +54,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
filezilla:
image: lscr.io/linuxserver/filezilla
image: lscr.io/linuxserver/filezilla:latest
container_name: filezilla
environment:
- PUID=1000
@ -78,7 +78,7 @@ docker run -d \
-p 3000:3000 \
-v /path/to/config:/config \
--restart unless-stopped \
lscr.io/linuxserver/filezilla
lscr.io/linuxserver/filezilla:latest
```
## Parameters
@ -155,7 +155,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' filezilla`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/filezilla`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/filezilla:latest`
## Versions

20
images/docker-firefox.md
Wyświetl plik

@ -21,17 +21,17 @@ title: firefox
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/firefox` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/firefox:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -54,7 +54,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
firefox:
image: lscr.io/linuxserver/firefox
image: lscr.io/linuxserver/firefox:latest
container_name: firefox
environment:
- PUID=1000
@ -80,7 +80,7 @@ docker run -d \
-v /path/to/config:/config \
--shm-size="1gb" \
--restart unless-stopped \
lscr.io/linuxserver/firefox
lscr.io/linuxserver/firefox:latest
```
## Parameters
@ -158,7 +158,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' firefox`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/firefox`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/firefox:latest`
## Versions

21
images/docker-fleet.md
Wyświetl plik

@ -21,17 +21,17 @@ title: fleet
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/fleet` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/fleet:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -50,7 +50,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
fleet:
image: lscr.io/linuxserver/fleet
image: lscr.io/linuxserver/fleet:latest
container_name: fleet
environment:
- PUID=1000
@ -82,7 +82,7 @@ docker run -d \
-p 8080:8080 \
-v </path/to/appdata/config>:/config \
--restart unless-stopped \
lscr.io/linuxserver/fleet
lscr.io/linuxserver/fleet:latest
```
## Parameters
@ -163,10 +163,11 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' fleet`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/fleet`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/fleet:latest`
## Versions
* **02.05.22:** - Rebase to Alpine 3.15.
* **13.12.21:** - Add mitigations for CVE-2021-44228
* **26.04.20:** - Updated to keep in line with v2.0.0 branch of Fleet
* **19.12.19:** - Rebasing to alpine 3.11.

19
images/docker-foldingathome.md
Wyświetl plik

@ -21,16 +21,17 @@ title: foldingathome
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/foldingathome` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/foldingathome:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | latest |
| arm64 | arm64v8-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ❌ | |
## Application Setup
@ -61,7 +62,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
foldingathome:
image: lscr.io/linuxserver/foldingathome
image: lscr.io/linuxserver/foldingathome:latest
container_name: foldingathome
environment:
- PUID=1000
@ -87,7 +88,7 @@ docker run -d \
-p 36330:36330 `#optional` \
-v /path/to/data:/config \
--restart unless-stopped \
lscr.io/linuxserver/foldingathome
lscr.io/linuxserver/foldingathome:latest
```
## Parameters
@ -165,7 +166,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' foldingathome`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/foldingathome`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/foldingathome:latest`
## Versions

20
images/docker-freshrss.md
Wyświetl plik

@ -21,17 +21,17 @@ title: freshrss
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/freshrss` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/freshrss:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -52,7 +52,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
freshrss:
image: lscr.io/linuxserver/freshrss
image: lscr.io/linuxserver/freshrss:latest
container_name: freshrss
environment:
- PUID=1000
@ -76,7 +76,7 @@ docker run -d \
-p 80:80 \
-v /path/to/data:/config \
--restart unless-stopped \
lscr.io/linuxserver/freshrss
lscr.io/linuxserver/freshrss:latest
```
## Parameters
@ -153,7 +153,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' freshrss`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/freshrss`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/freshrss:latest`
## Versions

236
images/docker-gmail-order-bot.md
Wyświetl plik

@ -1,129 +1,36 @@
# [lsiodev/gmail-order-bot](https://github.com/linuxserver/docker-gmail-order-bot)
---
title: gmail-order-bot
---
<!-- DO NOT EDIT THIS FILE MANUALLY -->
<!-- Please read the https://github.com/lsiodev/docker-gmail-order-bot/blob/master/.github/CONTRIBUTING.md -->
[![GitHub Stars](https://img.shields.io/github/stars/lsiodev/docker-gmail-order-bot.svg?color=94398d&labelColor=555555&logoColor=ffffff&style=for-the-badge&logo=github)](https://github.com/linuxserver/docker-gmail-order-bot)
[![GitHub Release](https://img.shields.io/github/release/lsiodev/docker-gmail-order-bot.svg?color=94398d&labelColor=555555&logoColor=ffffff&style=for-the-badge&logo=github)](https://github.com/linuxserver/docker-gmail-order-bot/releases)
[![GitHub Package Repository](https://img.shields.io/static/v1.svg?color=94398d&labelColor=555555&logoColor=ffffff&style=for-the-badge&label=linuxserver.io&message=GitHub%20Package&logo=github)](https://github.com/linuxserver/docker-gmail-order-bot/packages)
[![GitLab Container Registry](https://img.shields.io/static/v1.svg?color=94398d&labelColor=555555&logoColor=ffffff&style=for-the-badge&label=linuxserver.io&message=GitLab%20Registry&logo=gitlab)](https://gitlab.com/Linuxserver.io/docker-gmail-order-bot/container_registry)
[![MicroBadger Layers](https://img.shields.io/microbadger/layers/lsiodev/gmail-order-bot.svg?color=94398d&labelColor=555555&logoColor=ffffff&style=for-the-badge)](https://microbadger.com/images/lsiodev/gmail-order-bot "Get your own version badge on microbadger.com")
# [lsiodev/gmail-order-bot](https://github.com/lsiodev/docker-gmail-order-bot)
[![Scarf.io pulls](https://scarf.sh/installs-badge/lsiodev-ci/lsiodev%2Fgmail-order-bot?color=94398d&label-color=555555&logo-color=ffffff&style=for-the-badge&package-type=docker)](https://scarf.sh/gateway/lsiodev-ci/docker/lsiodev%2Fgmail-order-bot)
[![GitHub Stars](https://img.shields.io/github/stars/lsiodev/docker-gmail-order-bot.svg?color=94398d&labelColor=555555&logoColor=ffffff&style=for-the-badge&logo=github)](https://github.com/lsiodev/docker-gmail-order-bot)
[![GitHub Release](https://img.shields.io/github/release/lsiodev/docker-gmail-order-bot.svg?color=94398d&labelColor=555555&logoColor=ffffff&style=for-the-badge&logo=github)](https://github.com/lsiodev/docker-gmail-order-bot/releases)
[![GitHub Package Repository](https://img.shields.io/static/v1.svg?color=94398d&labelColor=555555&logoColor=ffffff&style=for-the-badge&label=linuxserver.io&message=GitHub%20Package&logo=github)](https://github.com/lsiodev/docker-gmail-order-bot/packages)
[![GitLab Container Registry](https://img.shields.io/static/v1.svg?color=94398d&labelColor=555555&logoColor=ffffff&style=for-the-badge&label=linuxserver.io&message=GitLab%20Registry&logo=gitlab)](https://gitlab.com/linuxserver.io/docker-gmail-order-bot/container_registry)
[![Quay.io](https://img.shields.io/static/v1.svg?color=94398d&labelColor=555555&logoColor=ffffff&style=for-the-badge&label=linuxserver.io&message=Quay.io)](https://quay.io/repository/linuxserver.io/gmail-order-bot)
[![Docker Pulls](https://img.shields.io/docker/pulls/lsiodev/gmail-order-bot.svg?color=94398d&labelColor=555555&logoColor=ffffff&style=for-the-badge&label=pulls&logo=docker)](https://hub.docker.com/r/lsiodev/gmail-order-bot)
[![Docker Stars](https://img.shields.io/docker/stars/lsiodev/gmail-order-bot.svg?color=94398d&labelColor=555555&logoColor=ffffff&style=for-the-badge&label=stars&logo=docker)](https://hub.docker.com/r/lsiodev/gmail-order-bot)
[![Jenkins Build](https://img.shields.io/jenkins/build?labelColor=555555&logoColor=ffffff&style=for-the-badge&jobUrl=https%3A%2F%2Fci.linuxserver.io%2Fjob%2FDocker-Pipeline-Builders%2Fjob%2Fdocker-gmail-order-bot%2Fjob%2Fmaster%2F&logo=jenkins)](https://ci.linuxserver.io/job/Docker-Pipeline-Builders/job/docker-gmail-order-bot/job/master/)
[Gmail-order-bot](https://developers.google.com/gmail/api) - A bot used to leverage a Gmail account as an order messaging service to consume email orders from [Nano Checkout](https://github.com/linuxserver/nano-checkout) and process them using any custom logic you choose.
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `ghcr.io/lsiodev/gmail-order-bot` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/lsiodev/gmail-order-bot:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
## Usage
Here are some example snippets to help you get started creating a container from this image.
### docker-compose ([recommended](https://docs.linuxserver.io/general/docker-compose))
Compatible with docker-compose v2 schemas.
```yaml
---
version: "2.1"
services:
gmail-order-bot:
image: ghcr.io/lsiodev/gmail-order-bot
container_name: gmail-order-bot
environment:
- PUID=1000
- PGID=1000
- BOT_NAME=discord
- LOOP_TIME=60
volumes:
- /path/to/data:/config
restart: unless-stopped
```
### docker cli
```
docker run -d \
--name=gmail-order-bot \
-e PUID=1000 \
-e PGID=1000 \
-e BOT_NAME=discord \
-e LOOP_TIME=60 \
-v /path/to/data:/config \
--restart unless-stopped \
ghcr.io/lsiodev/gmail-order-bot
```
## Parameters
Docker images are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate `<external>:<internal>` respectively. For example, `-p 8080:80` would expose port `80` from inside the container to be accessible from the host's IP on port `8080` outside the container.
### Ports (`-p`)
| Parameter | Function |
| :----: | --- |
### Environment Variables (`-e`)
| Env | Function |
| :----: | --- |
| `PUID=1000` | for UserID - see below for explanation |
| `PGID=1000` | for GroupID - see below for explanation |
| `BOT_NAME=discord` | On successful order receive send the order payload to this bot (default bots are located in root/defaults/bots) |
| `LOOP_TIME=60` | Time in seconds to reach into gmail and get new messages to process |
### Volume Mappings (`-v`)
| Volume | Function |
| :----: | --- |
| `/config` | Path to gmail tokens and custom/default bots |
## Environment variables from files (Docker secrets)
You can set any environment variable from a file by using a special prepend `FILE__`.
As an example:
```
-e FILE__PASSWORD=/run/secrets/mysecretpassword
```
Will set the environment variable `PASSWORD` based on the contents of the `/run/secrets/mysecretpassword` file.
## Umask for running applications
For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional `-e UMASK=022` setting.
Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up [here](https://en.wikipedia.org/wiki/Umask) before asking for support.
## User / Group Identifiers
When using volumes (`-v` flags), permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user `PUID` and group `PGID`.
Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.
In this instance `PUID=1000` and `PGID=1000`, to find yours use `id user` as below:
```
$ id username
uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)
```
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -167,14 +74,109 @@ In order to use this bot you will need to perform the following setup steps:
When the container starts if you are using a custom bot located in `/config/bots` it will install the node modules included in it's package.json, do not use system level node modules this container is Alpine based and it will cause conflicts.
From there the bot will loop in for your defined timeout and pull in emails and spit out orders to your destination.
From there the bot will loop in for your defined timeout and pull in emails and spit out orders to your destination.
## Usage
To help you get started creating a container from this image you can either use docker-compose or the docker cli.
### docker-compose (recommended, [click here for more info](https://docs.linuxserver.io/general/docker-compose))
```yaml
---
version: "2.1"
services:
gmail-order-bot:
image: lscr.io/lsiodev/gmail-order-bot:latest
container_name: gmail-order-bot
environment:
- PUID=1000
- PGID=1000
- BOT_NAME=discord
- LOOP_TIME=60
volumes:
- /path/to/data:/config
restart: unless-stopped
```
### docker cli ([click here for more info](https://docs.docker.com/engine/reference/commandline/cli/))
```bash
docker run -d \
--name=gmail-order-bot \
-e PUID=1000 \
-e PGID=1000 \
-e BOT_NAME=discord \
-e LOOP_TIME=60 \
-v /path/to/data:/config \
--restart unless-stopped \
lscr.io/lsiodev/gmail-order-bot:latest
```
## Parameters
Docker images are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate `<external>:<internal>` respectively. For example, `-p 8080:80` would expose port `80` from inside the container to be accessible from the host's IP on port `8080` outside the container.
### Ports (`-p`)
| Parameter | Function |
| :----: | --- |
### Environment Variables (`-e`)
| Env | Function |
| :----: | --- |
| `PUID=1000` | for UserID - see below for explanation |
| `PGID=1000` | for GroupID - see below for explanation |
| `BOT_NAME=discord` | On successful order receive send the order payload to this bot (default bots are located in root/defaults/bots) |
| `LOOP_TIME=60` | Time in seconds to reach into gmail and get new messages to process |
### Volume Mappings (`-v`)
| Volume | Function |
| :----: | --- |
| `/config` | Path to gmail tokens and custom/default bots |
#### Miscellaneous Options
| Parameter | Function |
| :-----: | --- |
## Environment variables from files (Docker secrets)
You can set any environment variable from a file by using a special prepend `FILE__`.
As an example:
```bash
-e FILE__PASSWORD=/run/secrets/mysecretpassword
```
Will set the environment variable `PASSWORD` based on the contents of the `/run/secrets/mysecretpassword` file.
## Umask for running applications
For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional `-e UMASK=022` setting.
Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up [here](https://en.wikipedia.org/wiki/Umask) before asking for support.
## User / Group Identifiers
When using volumes (`-v` flags), permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user `PUID` and group `PGID`.
Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.
In this instance `PUID=1000` and `PGID=1000`, to find yours use `id user` as below:
```bash
$ id username
uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)
```
## Docker Mods
[![Docker Mods](https://img.shields.io/badge/dynamic/yaml?color=94398d&labelColor=555555&logoColor=ffffff&style=for-the-badge&label=gmail-order-bot&query=%24.mods%5B%27gmail-order-bot%27%5D.mod_count&url=https%3A%2F%2Fraw.githubusercontent.com%2Flinuxserver%2Fdocker-mods%2Fmaster%2Fmod-list.yml)](https://mods.linuxserver.io/?mod=gmail-order-bot "view available mods for this container.") [![Docker Universal Mods](https://img.shields.io/badge/dynamic/yaml?color=94398d&labelColor=555555&logoColor=ffffff&style=for-the-badge&label=universal&query=%24.mods%5B%27universal%27%5D.mod_count&url=https%3A%2F%2Fraw.githubusercontent.com%2Flinuxserver%2Fdocker-mods%2Fmaster%2Fmod-list.yml)](https://mods.linuxserver.io/?mod=universal "view available universal mods.")
We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.
We publish various [Docker Mods](https://github.com/lsiodev/docker-mods) to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.
## Support Info
@ -185,7 +187,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' gmail-order-bot`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' ghcr.io/lsiodev/gmail-order-bot`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/lsiodev/gmail-order-bot:latest`
## Versions

20
images/docker-grav.md
Wyświetl plik

@ -21,17 +21,17 @@ title: grav
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/grav` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/grav:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -48,7 +48,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
grav:
image: lscr.io/linuxserver/grav
image: lscr.io/linuxserver/grav:latest
container_name: grav
environment:
- PUID=1000
@ -72,7 +72,7 @@ docker run -d \
-p 80:80 \
-v /path/to/appdata/config:/config \
--restart unless-stopped \
lscr.io/linuxserver/grav
lscr.io/linuxserver/grav:latest
```
## Parameters
@ -149,7 +149,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' grav`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/grav`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/grav:latest`
## Versions

20
images/docker-grocy.md
Wyświetl plik

@ -25,17 +25,17 @@ For more information on grocy visit their website and check it out: https://groc
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/grocy` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/grocy:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -53,7 +53,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
grocy:
image: lscr.io/linuxserver/grocy
image: lscr.io/linuxserver/grocy:latest
container_name: grocy
environment:
- PUID=1000
@ -77,7 +77,7 @@ docker run -d \
-p 9283:80 \
-v /path/to/data:/config \
--restart unless-stopped \
lscr.io/linuxserver/grocy
lscr.io/linuxserver/grocy:latest
```
## Parameters
@ -154,7 +154,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' grocy`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/grocy`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/grocy:latest`
## Versions

20
images/docker-guacd.md
Wyświetl plik

@ -21,17 +21,17 @@ title: guacd
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/guacd` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/guacd:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -48,7 +48,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
guacd:
image: lscr.io/linuxserver/guacd
image: lscr.io/linuxserver/guacd:latest
container_name: guacd
ports:
- 4822:4822
@ -62,7 +62,7 @@ docker run -d \
--name=guacd \
-p 4822:4822 \
--restart unless-stopped \
lscr.io/linuxserver/guacd
lscr.io/linuxserver/guacd:latest
```
## Parameters
@ -122,7 +122,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' guacd`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/guacd`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/guacd:latest`
## Versions

21
images/docker-headphones.md
Wyświetl plik

@ -21,17 +21,18 @@ title: headphones
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/headphones` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/headphones:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Usage
@ -44,7 +45,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
headphones:
image: lscr.io/linuxserver/headphones
image: lscr.io/linuxserver/headphones:latest
container_name: headphones
environment:
- PUID=1000
@ -72,7 +73,7 @@ docker run -d \
-v </path/to/downloads>:/downloads \
-v </path/to/music>:/music \
--restart unless-stopped \
lscr.io/linuxserver/headphones
lscr.io/linuxserver/headphones:latest
```
## Parameters
@ -151,7 +152,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' headphones`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/headphones`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/headphones:latest`
## Versions

20
images/docker-healthchecks.md
Wyświetl plik

@ -21,17 +21,17 @@ title: healthchecks
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/healthchecks` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/healthchecks:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -48,7 +48,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
healthchecks:
image: lscr.io/linuxserver/healthchecks
image: lscr.io/linuxserver/healthchecks:latest
container_name: healthchecks
environment:
- PUID=1000
@ -100,7 +100,7 @@ docker run -d \
-p 8000:8000 \
-v <path to data on host>:/config \
--restart unless-stopped \
lscr.io/linuxserver/healthchecks
lscr.io/linuxserver/healthchecks:latest
```
## Parameters
@ -191,7 +191,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' healthchecks`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/healthchecks`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/healthchecks:latest`
## Versions

19
images/docker-hedgedoc.md
Wyświetl plik

@ -23,17 +23,17 @@ HedgeDoc is a real-time, multi-platform collaborative markdown note editor. Thi
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/hedgedoc` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/hedgedoc:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -114,7 +114,7 @@ docker run -d \
-p 3000:3000 \
-v /path/to/appdata:/config \
--restart unless-stopped \
lscr.io/linuxserver/hedgedoc
lscr.io/linuxserver/hedgedoc:latest
```
## Parameters
@ -200,10 +200,11 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' hedgedoc`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/hedgedoc`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/hedgedoc:latest`
## Versions
* **10.04.22:** - Use python3 to build node sqlite3.
* **10.02.22:** - Rebase to Alpine 3.15.
* **09.02.22:** - Add optional var `CMD_PORT` that is needed for accessing at port other than 80, 443 and 3000.
* **09.12.21:** - Add optional var `CMD_PROTOCOL_USESSL` that is needed for reverse proxy.

30
images/docker-heimdall.md
Wyświetl plik

@ -23,26 +23,26 @@ Why not use it as your browser start page? It even has the ability to include a
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/heimdall` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/heimdall:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Version Tags
This image provides various versions that are available via tags. `latest` tag usually provides the latest stable version. Others are considered under development and caution must be exercised when using them.
This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.
| Tag | Description |
| :----: | --- |
| latest | Stable Heimdall releases. |
| development | Latest commit from the github master branch. |
| Tag | Available | Description |
| :----: | :----: |--- |
| latest | ✅ | Stable Heimdall releases. |
| development | ✅ | Latest commit from the github master branch. |
## Application Setup
@ -64,7 +64,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
heimdall:
image: lscr.io/linuxserver/heimdall
image: lscr.io/linuxserver/heimdall:latest
container_name: heimdall
environment:
- PUID=1000
@ -90,7 +90,7 @@ docker run -d \
-p 443:443 \
-v </path/to/appdata/config>:/config \
--restart unless-stopped \
lscr.io/linuxserver/heimdall
lscr.io/linuxserver/heimdall:latest
```
## Parameters
@ -168,7 +168,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' heimdall`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/heimdall`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/heimdall:latest`
## Versions

22
images/docker-homeassistant.md
Wyświetl plik

@ -21,17 +21,17 @@ title: homeassistant
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/homeassistant` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/homeassistant:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -50,7 +50,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
homeassistant:
image: lscr.io/linuxserver/homeassistant
image: lscr.io/linuxserver/homeassistant:latest
container_name: homeassistant
network_mode: host
environment:
@ -79,7 +79,7 @@ docker run -d \
-v /path/to/data:/config \
--device /path/to/device:/path/to/device `#optional` \
--restart unless-stopped \
lscr.io/linuxserver/homeassistant
lscr.io/linuxserver/homeassistant:latest
```
#### Host vs. Bridge
@ -179,10 +179,12 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' homeassistant`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/homeassistant`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/homeassistant:latest`
## Versions
* **07.05.22:** - Build matplotlib with the same Numpy version as HA req.
* **31.03.22:** - Install pycups.
* **07.03.22:** - Install PySwitchbot.
* **02.03.22:** - Update pip and use legacy resolver, clean up temp python files, reduce image size.
* **04.02.22:** - Always compile grpcio on arm32v7 due to pypi pushing a glibc only wheel.

20
images/docker-htpcmanager.md
Wyświetl plik

@ -21,17 +21,17 @@ title: htpcmanager
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/htpcmanager` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/htpcmanager:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -48,7 +48,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
htpcmanager:
image: lscr.io/linuxserver/htpcmanager
image: lscr.io/linuxserver/htpcmanager:latest
container_name: htpcmanager
environment:
- PUID=1000
@ -72,7 +72,7 @@ docker run -d \
-p 8085:8085 \
-v /path/to/appdata/config:/config \
--restart unless-stopped \
lscr.io/linuxserver/htpcmanager
lscr.io/linuxserver/htpcmanager:latest
```
## Parameters
@ -149,7 +149,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' htpcmanager`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/htpcmanager`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/htpcmanager:latest`
## Versions

31
images/docker-jackett.md
Wyświetl plik

@ -21,26 +21,26 @@ title: jackett
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/jackett` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/jackett:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Version Tags
This image provides various versions that are available via tags. `latest` tag usually provides the latest stable version. Others are considered under development and caution must be exercised when using them.
This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.
| Tag | Description |
| :----: | --- |
| latest | Stable Jackett Releases |
| development | Latest Jackett Releases |
| Tag | Available | Description |
| :----: | :----: |--- |
| latest | ✅ | Stable Jackett Releases |
| development | ✅ | Latest Jackett Releases |
## Application Setup
@ -60,7 +60,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
jackett:
image: lscr.io/linuxserver/jackett
image: lscr.io/linuxserver/jackett:latest
container_name: jackett
environment:
- PUID=1000
@ -90,7 +90,7 @@ docker run -d \
-v <path to data>:/config \
-v <path to blackhole>:/downloads \
--restart unless-stopped \
lscr.io/linuxserver/jackett
lscr.io/linuxserver/jackett:latest
```
## Parameters
@ -170,10 +170,11 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' jackett`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/jackett`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/jackett:latest`
## Versions
* **10.05.22:** - Rebase to Ubuntu Focal.
* **24.05.20:** - Allow user to optionally enable auto updates.
* **31.12.19:** - Remove agressive startup chowning.
* **23.03.19:** - Switching to new Base images, shift to arm32v7 tag.

30
images/docker-jellyfin.md
Wyświetl plik

@ -21,26 +21,26 @@ title: jellyfin
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/jellyfin` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/jellyfin:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Version Tags
This image provides various versions that are available via tags. `latest` tag usually provides the latest stable version. Others are considered under development and caution must be exercised when using them.
This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.
| Tag | Description |
| :----: | --- |
| latest | Stable Jellyfin releases |
| nightly | Nightly Jellyfin releases |
| Tag | Available | Description |
| :----: | :----: |--- |
| latest | ✅ | Stable Jellyfin releases |
| nightly | ✅ | Nightly Jellyfin releases |
## Application Setup
@ -97,7 +97,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
jellyfin:
image: lscr.io/linuxserver/jellyfin
image: lscr.io/linuxserver/jellyfin:latest
container_name: jellyfin
environment:
- PUID=1000
@ -133,7 +133,7 @@ docker run -d \
-v /path/to/tvseries:/data/tvshows \
-v /path/to/movies:/data/movies \
--restart unless-stopped \
lscr.io/linuxserver/jellyfin
lscr.io/linuxserver/jellyfin:latest
```
## Parameters
@ -231,7 +231,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' jellyfin`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/jellyfin`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/jellyfin:latest`
## Versions

8
images/docker-jenkins-builder.md
Wyświetl plik

@ -10,7 +10,7 @@ Expects to run as part of the LSIO CI process. Not for public consumption.
## Running against remote project
```shell
```bash
docker run --rm \
-e CONTAINER_NAME=${CONTAINER_NAME} \
-v ${TEMPDIR}:/ansible/jenkins \
@ -21,7 +21,7 @@ docker run --rm \
If you need to test functionality just navigate to the folder with the jenkins-vars.yml and run:
```shell
```bash
docker pull lscr.io/linuxserver/jenkins-builder:latest && \
docker run --rm \
-v $(pwd):/tmp \
@ -37,7 +37,7 @@ Newly generated files (including `README.md`, `Jenkinsfile`, issue templates, et
If you want to make local modifications to these images for development purposes or just to customize the logic:
```shell
```bash
git clone https://github.com/linuxserver/docker-jenkins-builder.git
cd docker-jenkins-builder
docker build \
@ -48,7 +48,7 @@ docker build \
The ARM variants can be built on x86_64 hardware using `multiarch/qemu-user-static`
```shell
```bash
docker run --rm --privileged multiarch/qemu-user-static:register --reset
```

25
images/docker-kanzi.md
Wyświetl plik

@ -21,17 +21,17 @@ title: kanzi
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/kanzi` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/kanzi:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -69,6 +69,11 @@ The architectures supported by this image are:
}
```
### Strict reverse proxies
This image uses a self-signed certificate by default. This naturally means the scheme is `https`.
If you are using a reverse proxy which validates certificates, you need to [disable this check for the container](https://docs.linuxserver.io/faq#strict-proxy).
## Usage
To help you get started creating a container from this image you can either use docker-compose or the docker cli.
@ -80,7 +85,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
kanzi:
image: lscr.io/linuxserver/kanzi
image: lscr.io/linuxserver/kanzi:latest
container_name: kanzi
environment:
- PUID=1000
@ -108,7 +113,7 @@ docker run -d \
-p 8000:8000 \
-v </path/to/appdata/config>:/config \
--restart unless-stopped \
lscr.io/linuxserver/kanzi
lscr.io/linuxserver/kanzi:latest
```
## Parameters
@ -187,7 +192,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' kanzi`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/kanzi`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/kanzi:latest`
## Versions

20
images/docker-kdenlive.md
Wyświetl plik

@ -21,17 +21,17 @@ title: kdenlive
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/kdenlive` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/kdenlive:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -96,7 +96,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
kdenlive:
image: lscr.io/linuxserver/kdenlive
image: lscr.io/linuxserver/kdenlive:latest
container_name: kdenlive
security_opt:
- seccomp:unconfined #optional
@ -132,7 +132,7 @@ docker run -d \
--device /dev/dri:/dev/dri `#optional` \
--shm-size="1gb" `#optional` \
--restart unless-stopped \
lscr.io/linuxserver/kdenlive
lscr.io/linuxserver/kdenlive:latest
```
## Parameters
@ -219,7 +219,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' kdenlive`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/kdenlive`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/kdenlive:latest`
## Versions

21
images/docker-lazylibrarian.md
Wyświetl plik

@ -21,17 +21,17 @@ title: lazylibrarian
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/lazylibrarian` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/lazylibrarian:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -68,7 +68,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
lazylibrarian:
image: lscr.io/linuxserver/lazylibrarian
image: lscr.io/linuxserver/lazylibrarian:latest
container_name: lazylibrarian
environment:
- PUID=1000
@ -98,7 +98,7 @@ docker run -d \
-v /path/to/downloads/:/downloads \
-v /path/to/data/:/books `#optional` \
--restart unless-stopped \
lscr.io/linuxserver/lazylibrarian
lscr.io/linuxserver/lazylibrarian:latest
```
## Parameters
@ -178,10 +178,11 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lazylibrarian`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/lazylibrarian`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/lazylibrarian:latest`
## Versions
* **07.05.22:** - Rebase to Ubuntu Focal.
* **22.05.21:** - Make the paths clearer to the user, remove optional volume.
* **17.05.21:** - Add linuxserver wheel index.
* **23.10.19:** - Changed gitlab download link.

20
images/docker-ldap-auth.md
Wyświetl plik

@ -21,17 +21,17 @@ title: ldap-auth
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/ldap-auth` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/ldap-auth:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -51,7 +51,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
ldap-auth:
image: lscr.io/linuxserver/ldap-auth
image: lscr.io/linuxserver/ldap-auth:latest
container_name: ldap-auth
environment:
- TZ=Europe/London
@ -76,7 +76,7 @@ docker run -d \
-p 8888:8888 \
-p 9000:9000 \
--restart unless-stopped \
lscr.io/linuxserver/ldap-auth
lscr.io/linuxserver/ldap-auth:latest
```
## Parameters
@ -141,7 +141,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' ldap-auth`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/ldap-auth`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/ldap-auth:latest`
## Versions

20
images/docker-libreoffice.md
Wyświetl plik

@ -21,17 +21,17 @@ title: libreoffice
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/libreoffice` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/libreoffice:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -54,7 +54,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
libreoffice:
image: lscr.io/linuxserver/libreoffice
image: lscr.io/linuxserver/libreoffice:latest
container_name: libreoffice
environment:
- PUID=1000
@ -78,7 +78,7 @@ docker run -d \
-p 3000:3000 \
-v /path/to/config:/config \
--restart unless-stopped \
lscr.io/linuxserver/libreoffice
lscr.io/linuxserver/libreoffice:latest
```
## Parameters
@ -155,7 +155,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' libreoffice`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/libreoffice`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/libreoffice:latest`
## Versions

20
images/docker-librespeed.md
Wyświetl plik

@ -22,17 +22,17 @@ No Flash, No Java, No Websocket, No Bullshit.
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/librespeed` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/librespeed:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -57,7 +57,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
librespeed:
image: lscr.io/linuxserver/librespeed
image: lscr.io/linuxserver/librespeed:latest
container_name: librespeed
environment:
- PUID=1000
@ -97,7 +97,7 @@ docker run -d \
-p 80:80 \
-v /path/to/appdata/config:/config \
--restart unless-stopped \
lscr.io/linuxserver/librespeed
lscr.io/linuxserver/librespeed:latest
```
## Parameters
@ -182,7 +182,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' librespeed`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/librespeed`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/librespeed:latest`
## Versions

34
images/docker-lidarr.md
Wyświetl plik

@ -21,27 +21,27 @@ title: lidarr
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/lidarr` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/lidarr:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Version Tags
This image provides various versions that are available via tags. `latest` tag usually provides the latest stable version. Others are considered under development and caution must be exercised when using them.
This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.
| Tag | Description |
| :----: | --- |
| latest | Stable Lidarr releases. |
| develop | Develop Lidarr Releases. |
| nightly | Nightly Lidarr Releases. |
| Tag | Available | Description |
| :----: | :----: |--- |
| latest | ✅ | Stable Lidarr releases. |
| develop | ✅ | Develop Lidarr Releases. |
| nightly | ✅ | Nightly Lidarr Releases. |
## Application Setup
@ -70,7 +70,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
lidarr:
image: lscr.io/linuxserver/lidarr
image: lscr.io/linuxserver/lidarr:latest
container_name: lidarr
environment:
- PUID=1000
@ -98,7 +98,7 @@ docker run -d \
-v /path/to/music:/music `#optional` \
-v /path/to/downloads:/downloads `#optional` \
--restart unless-stopped \
lscr.io/linuxserver/lidarr
lscr.io/linuxserver/lidarr:latest
```
## Parameters
@ -177,10 +177,12 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lidarr`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/lidarr`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/lidarr:latest`
## Versions
* **06.05.22:** - Rebase master branch to Focal.
* **06.05.22:** - Rebase develop branch to Alpine.
* **04.02.22:** - Rebase nightly branch to Alpine, deprecate nightly-alpine branch.
* **30.12.21:** - Add nightly-alpine branch.
* **01.08.21:** - Add libchromaprint-tools.

20
images/docker-limnoria.md
Wyświetl plik

@ -21,17 +21,17 @@ title: limnoria
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/limnoria` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/limnoria:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -78,7 +78,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
limnoria:
image: lscr.io/linuxserver/limnoria
image: lscr.io/linuxserver/limnoria:latest
container_name: limnoria
environment:
- PUID=1000
@ -102,7 +102,7 @@ docker run -d \
-p 8080:8080 \
-v path/to/config:/config \
--restart unless-stopped \
lscr.io/linuxserver/limnoria
lscr.io/linuxserver/limnoria:latest
```
## Parameters
@ -179,7 +179,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' limnoria`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/limnoria`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/limnoria:latest`
## Versions

18
images/docker-lychee.md
Wyświetl plik

@ -25,17 +25,17 @@ Please note that the v4 upgrade process resets ALL password-protected albums. An
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/lychee` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/lychee:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -106,7 +106,7 @@ docker run -d \
-v /path/to/config:/config \
-v /path/to/pictures:/pictures \
--restart unless-stopped \
lscr.io/linuxserver/lychee
lscr.io/linuxserver/lychee:latest
```
## Parameters
@ -188,7 +188,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lychee`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/lychee`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/lychee:latest`
## Versions

20
images/docker-mariadb.md
Wyświetl plik

@ -21,17 +21,17 @@ title: mariadb
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/mariadb` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/mariadb:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -88,7 +88,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
mariadb:
image: lscr.io/linuxserver/mariadb
image: lscr.io/linuxserver/mariadb:latest
container_name: mariadb
environment:
- PUID=1000
@ -122,7 +122,7 @@ docker run -d \
-p 3306:3306 \
-v path_to_data:/config \
--restart unless-stopped \
lscr.io/linuxserver/mariadb
lscr.io/linuxserver/mariadb:latest
```
## Parameters
@ -204,7 +204,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' mariadb`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/mariadb`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/mariadb:latest`
## Versions

20
images/docker-medusa.md
Wyświetl plik

@ -21,17 +21,17 @@ title: medusa
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/medusa` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/medusa:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -50,7 +50,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
medusa:
image: lscr.io/linuxserver/medusa
image: lscr.io/linuxserver/medusa:latest
container_name: medusa
environment:
- PUID=1000
@ -78,7 +78,7 @@ docker run -d \
-v <path to downloads>:/downloads \
-v <path to tv shows>:/tv \
--restart unless-stopped \
lscr.io/linuxserver/medusa
lscr.io/linuxserver/medusa:latest
```
## Parameters
@ -157,7 +157,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' medusa`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/medusa`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/medusa:latest`
## Versions

31
images/docker-minetest.md
Wyświetl plik

@ -21,22 +21,26 @@ title: minetest
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/minetest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/minetest:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
You can find the world maps, mods folder and config files in /config/.minetest.
If you want to override the advertised port, ensure you add --port in your CLI_ARGS AND ensure the internal port reflects the change, ie;
if you set your advertised port to 40000 with --port 40000 then your ports declaration should be 40000:40000/udp
Client and server must be the same version, please browse the tags here to pull the appropriate version for your server:
https://hub.docker.com/r/linuxserver/minetest/tags
@ -52,13 +56,13 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
minetest:
image: lscr.io/linuxserver/minetest
image: lscr.io/linuxserver/minetest:latest
container_name: minetest
environment:
- PUID=1000
- PGID=1000
- TZ=Europe/London
- CLI_ARGS="--gameid minetest" #optional
- CLI_ARGS="--gameid minetest --port 30000" #optional
volumes:
- /path/to/data:/config/.minetest
ports:
@ -74,11 +78,11 @@ docker run -d \
-e PUID=1000 \
-e PGID=1000 \
-e TZ=Europe/London \
-e CLI_ARGS="--gameid minetest" `#optional` \
-e CLI_ARGS="--gameid minetest --port 30000" `#optional` \
-p 30000:30000/udp \
-v /path/to/data:/config/.minetest \
--restart unless-stopped \
lscr.io/linuxserver/minetest
lscr.io/linuxserver/minetest:latest
```
## Parameters
@ -98,7 +102,7 @@ Docker images are configured using parameters passed at runtime (such as those a
| `PUID=1000` | for UserID - see below for explanation |
| `PGID=1000` | for GroupID - see below for explanation |
| `TZ=Europe/London` | Specify a timezone to use EG Europe/London. |
| `CLI_ARGS="--gameid minetest"` | Optionally specify any [CLI variables](https://wiki.minetest.net/Command_line) you want to launch the app with |
| `CLI_ARGS="--gameid minetest --port 30000"` | Optionally specify any [CLI variables](https://wiki.minetest.net/Command_line) you want to launch the app with |
### Volume Mappings (`-v`)
@ -156,10 +160,11 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' minetest`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/minetest`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/minetest:latest`
## Versions
* **02.05.22:** - Allow specifying the advertised port.
* **17.03.22:** - Install forked irrlicht, add zstd.
* **19.01.22:** - Rebasing to alpine 3.15.
* **02.06.20:** - Rebasing to alpine 3.12.

20
images/docker-minisatip.md
Wyświetl plik

@ -21,17 +21,17 @@ title: minisatip
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/minisatip` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/minisatip:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -52,7 +52,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
minisatip:
image: lscr.io/linuxserver/minisatip
image: lscr.io/linuxserver/minisatip:latest
container_name: minisatip
environment:
- PUID=1000
@ -85,7 +85,7 @@ docker run -d \
-v </path/to/appdata/config>:/config \
--device /dev/dvb:/dev/dvb \
--restart unless-stopped \
lscr.io/linuxserver/minisatip
lscr.io/linuxserver/minisatip:latest
```
### Additional runtime parameters
@ -176,7 +176,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' minisatip`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/minisatip`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/minisatip:latest`
## Versions

22
images/docker-mstream.md
Wyświetl plik

@ -21,17 +21,17 @@ title: mstream
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/mstream` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/mstream:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -55,7 +55,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
mstream:
image: lscr.io/linuxserver/mstream
image: lscr.io/linuxserver/mstream:latest
container_name: mstream
environment:
- PUID=1000
@ -81,7 +81,7 @@ docker run -d \
-v /path/to/data:/config \
-v /path/to/music:/music \
--restart unless-stopped \
lscr.io/linuxserver/mstream
lscr.io/linuxserver/mstream:latest
```
## Parameters
@ -159,10 +159,12 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' mstream`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/mstream`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/mstream:latest`
## Versions
* **05.04.22:** - Move `sync` folder to `/config`.
* **02.04.22:** - Rebase to alpine 3.15. Fix ffmpeg download.
* **17.05.21:** - Deprecating the env vars `USER`, `PASSWORD` and `USE_JSON` as mStream v5 requires the use of `config.json`.
* **23.01.21:** - Rebasing to alpine 3.13.
* **01.06.20:** - Rebasing to alpine 3.12.

20
images/docker-muximux.md
Wyświetl plik

@ -21,17 +21,17 @@ title: muximux
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/muximux` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/muximux:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -49,7 +49,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
muximux:
image: lscr.io/linuxserver/muximux
image: lscr.io/linuxserver/muximux:latest
container_name: muximux
environment:
- PUID=1000
@ -73,7 +73,7 @@ docker run -d \
-p 80:80 \
-v <path to data>:/config \
--restart unless-stopped \
lscr.io/linuxserver/muximux
lscr.io/linuxserver/muximux:latest
```
## Parameters
@ -150,7 +150,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' muximux`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/muximux`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/muximux:latest`
## Versions

30
images/docker-mylar3.md
Wyświetl plik

@ -21,26 +21,26 @@ title: mylar3
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/mylar3` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/mylar3:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Version Tags
This image provides various versions that are available via tags. `latest` tag usually provides the latest stable version. Others are considered under development and caution must be exercised when using them.
This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.
| Tag | Description |
| :----: | --- |
| latest | Stable Mylar3 releases |
| nightly | Commits to Mylar3 `python3-dev` branch |
| Tag | Available | Description |
| :----: | :----: |--- |
| latest | ✅ | Stable Mylar3 releases |
| nightly | ✅ | Commits to Mylar3 `python3-dev` branch |
## Application Setup
@ -58,7 +58,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
mylar3:
image: lscr.io/linuxserver/mylar3
image: lscr.io/linuxserver/mylar3:latest
container_name: mylar3
environment:
- PUID=1000
@ -84,7 +84,7 @@ docker run -d \
-v /path/to/comics:/comics \
-v /path/to/downloads:/downloads \
--restart unless-stopped \
lscr.io/linuxserver/mylar3
lscr.io/linuxserver/mylar3:latest
```
## Parameters
@ -162,7 +162,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' mylar3`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/mylar3`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/mylar3:latest`
## Versions

16
images/docker-mysql-workbench.md
Wyświetl plik

@ -23,13 +23,15 @@ title: mysql-workbench
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/mysql-workbench` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/mysql-workbench:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ❌ | |
| armhf| ❌ | |
## Application Setup
@ -52,7 +54,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
mysql-workbench:
image: lscr.io/linuxserver/mysql-workbench
image: lscr.io/linuxserver/mysql-workbench:latest
container_name: mysql-workbench
environment:
- PUID=1000
@ -79,7 +81,7 @@ docker run -d \
-v /path/to/config:/config \
--cap-add="IPC_LOCK" \
--restart unless-stopped \
lscr.io/linuxserver/mysql-workbench
lscr.io/linuxserver/mysql-workbench:latest
```
## Parameters
@ -157,7 +159,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' mysql-workbench`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/mysql-workbench`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/mysql-workbench:latest`
## Versions

20
images/docker-nano-wallet.md
Wyświetl plik

@ -23,17 +23,17 @@ This container is a simple nginx wrapper for the light wallet located [here](htt
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/nano-wallet` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/nano-wallet:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -54,7 +54,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
nano-wallet:
image: lscr.io/linuxserver/nano-wallet
image: lscr.io/linuxserver/nano-wallet:latest
container_name: nano-wallet
ports:
- 80:80
@ -68,7 +68,7 @@ docker run -d \
--name=nano-wallet \
-p 80:80 \
--restart unless-stopped \
lscr.io/linuxserver/nano-wallet
lscr.io/linuxserver/nano-wallet:latest
```
## Parameters
@ -128,7 +128,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' nano-wallet`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/nano-wallet`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/nano-wallet:latest`
## Versions

29
images/docker-nano.md
Wyświetl plik

@ -21,25 +21,26 @@ title: nano
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/nano` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/nano:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ❌ | |
## Version Tags
This image provides various versions that are available via tags. `latest` tag usually provides the latest stable version. Others are considered under development and caution must be exercised when using them.
This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.
| Tag | Description |
| :----: | --- |
| latest | Stable Nano releases |
| beta | Beta Nano releases |
| Tag | Available | Description |
| :----: | :----: |--- |
| latest | ✅ | Stable Nano releases |
| beta | ✅ | Beta Nano releases |
## Application Setup
@ -239,7 +240,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
nano:
image: lscr.io/linuxserver/nano
image: lscr.io/linuxserver/nano:latest
container_name: nano
environment:
- PUID=1000
@ -281,7 +282,7 @@ docker run -d \
-p 7077:3001 \
-v /path/to/data:/config \
--restart unless-stopped \
lscr.io/linuxserver/nano
lscr.io/linuxserver/nano:latest
```
## Parameters
@ -367,7 +368,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' nano`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/nano`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/nano:latest`
## Versions

30
images/docker-netbootxyz.md
Wyświetl plik

@ -21,26 +21,26 @@ title: netbootxyz
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/netbootxyz` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/netbootxyz:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Version Tags
This image provides various versions that are available via tags. `latest` tag usually provides the latest stable version. Others are considered under development and caution must be exercised when using them.
This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.
| Tag | Description |
| :----: | --- |
| latest | Web application for full self hosting |
| tftp | TFTP server only with NETBOOT.XYZ boot files |
| Tag | Available | Description |
| :----: | :----: |--- |
| latest | ✅ | Web application for full self hosting |
| tftp | ✅ | TFTP server only with NETBOOT.XYZ boot files |
## Application Setup
@ -172,7 +172,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
netbootxyz:
image: lscr.io/linuxserver/netbootxyz
image: lscr.io/linuxserver/netbootxyz:latest
container_name: netbootxyz
environment:
- PUID=1000
@ -206,7 +206,7 @@ docker run -d \
-v /path/to/config:/config \
-v /path/to/assets:/assets `#optional` \
--restart unless-stopped \
lscr.io/linuxserver/netbootxyz
lscr.io/linuxserver/netbootxyz:latest
```
## Parameters
@ -288,7 +288,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' netbootxyz`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/netbootxyz`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/netbootxyz:latest`
## Versions

21
images/docker-netbox.md
Wyświetl plik

@ -21,17 +21,17 @@ title: netbox
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/netbox` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/netbox:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -50,7 +50,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
netbox:
image: lscr.io/linuxserver/netbox
image: lscr.io/linuxserver/netbox:latest
container_name: netbox
environment:
- PUID=1000
@ -114,7 +114,7 @@ docker run -d \
-p 8000:8000 \
-v <path to data on host>:/config \
--restart unless-stopped \
lscr.io/linuxserver/netbox
lscr.io/linuxserver/netbox:latest
```
## Parameters
@ -211,10 +211,11 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' netbox`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/netbox`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/netbox:latest`
## Versions
* **10.12.21:** - Remove py3-pillow package to fix dependency issue with 3.2.0.
* **10.12.21:** - Rebase to Alpine 3.15.
* **26.04.21:** - Added Redis database environment variables.
* **03.02.21:** - Added remote authentication environment variables.

37
images/docker-nextcloud.md
Wyświetl plik

@ -23,26 +23,26 @@ Where are your photos and documents? With Nextcloud you pick a server of your ch
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/nextcloud` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/nextcloud:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Version Tags
This image provides various versions that are available via tags. `latest` tag usually provides the latest stable version. Others are considered under development and caution must be exercised when using them.
This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.
| Tag | Description |
| :----: | --- |
| latest | Stable Nextcloud releases (currently php7) |
| php8 | Experimental php8 based Nextcloud releases |
| Tag | Available | Description |
| :----: | :----: |--- |
| latest | ✅ | Stable Nextcloud releases (currently php7) |
| php8 | ✅ | Experimental php8 based Nextcloud releases |
## Application Setup
@ -70,6 +70,11 @@ Nextcloud's built-in collaborative editing packages (Collabora/CODE and OnlyOffi
If (auto) installed, those built-in packages may cause instability and should be removed.
### Strict reverse proxies
This image uses a self-signed certificate by default. This naturally means the scheme is `https`.
If you are using a reverse proxy which validates certificates, you need to [disable this check for the container](https://docs.linuxserver.io/faq#strict-proxy).
## Usage
To help you get started creating a container from this image you can either use docker-compose or the docker cli.
@ -81,7 +86,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
nextcloud:
image: lscr.io/linuxserver/nextcloud
image: lscr.io/linuxserver/nextcloud:latest
container_name: nextcloud
environment:
- PUID=1000
@ -107,7 +112,7 @@ docker run -d \
-v /path/to/appdata:/config \
-v /path/to/data:/data \
--restart unless-stopped \
lscr.io/linuxserver/nextcloud
lscr.io/linuxserver/nextcloud:latest
```
## Parameters
@ -185,10 +190,12 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' nextcloud`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/nextcloud`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/nextcloud:latest`
## Versions
* **28.04.22:** - Increase OPCache interned strings buffered setting to 16.
* **14.04.22:** - Nginx default site config updated for v23 (existing users should delete `/config/nginx/site-confs/default` and restart the container). Fix LDAP connection.
* **11.09.21:** - Rebasing to alpine 3.14
* **21.03.21:** - Publish `php8` tag for testing.
* **25.02.21:** - Nginx default site config updated for v21 (existing users should delete `/config/nginx/site-confs/default` and restart the container).

20
images/docker-nginx.md
Wyświetl plik

@ -21,17 +21,17 @@ title: nginx
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/nginx` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/nginx:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -50,7 +50,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
nginx:
image: lscr.io/linuxserver/nginx
image: lscr.io/linuxserver/nginx:latest
container_name: nginx
environment:
- PUID=1000
@ -76,7 +76,7 @@ docker run -d \
-p 443:443 \
-v </path/to/appdata/config>:/config \
--restart unless-stopped \
lscr.io/linuxserver/nginx
lscr.io/linuxserver/nginx:latest
```
## Parameters
@ -154,7 +154,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' nginx`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/nginx`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/nginx:latest`
## Versions

20
images/docker-ngircd.md
Wyświetl plik

@ -21,17 +21,17 @@ title: ngircd
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/ngircd` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/ngircd:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -49,7 +49,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
ngircd:
image: lscr.io/linuxserver/ngircd
image: lscr.io/linuxserver/ngircd:latest
container_name: ngircd
environment:
- PUID=1000
@ -73,7 +73,7 @@ docker run -d \
-p 6667:6667 \
-v </path/to/ngircd/config>:/config \
--restart unless-stopped \
lscr.io/linuxserver/ngircd
lscr.io/linuxserver/ngircd:latest
```
## Parameters
@ -150,7 +150,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' ngircd`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/ngircd`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/ngircd:latest`
## Versions

20
images/docker-nntp2nntp.md
Wyświetl plik

@ -24,17 +24,17 @@ Whilst we know of no nntp2nntp security issues the [upstream code](https://githu
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/nntp2nntp` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/nntp2nntp:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v6-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -62,7 +62,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
nntp2nntp:
image: lscr.io/linuxserver/nntp2nntp
image: lscr.io/linuxserver/nntp2nntp:latest
container_name: nntp2nntp
environment:
- PUID=1000
@ -90,7 +90,7 @@ docker run -d \
-p 1563:1563 \
-v <path to data>:/config \
--restart unless-stopped \
lscr.io/linuxserver/nntp2nntp
lscr.io/linuxserver/nntp2nntp:latest
```
## Parameters
@ -169,7 +169,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' nntp2nntp`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/nntp2nntp`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/nntp2nntp:latest`
## Versions

30
images/docker-nzbget.md
Wyświetl plik

@ -21,26 +21,26 @@ title: nzbget
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/nzbget` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/nzbget:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Version Tags
This image provides various versions that are available via tags. `latest` tag usually provides the latest stable version. Others are considered under development and caution must be exercised when using them.
This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.
| Tag | Description |
| :----: | --- |
| latest | Stable nzbget releases |
| testing | nzbget pre-releases |
| Tag | Available | Description |
| :----: | :----: |--- |
| latest | ✅ | Stable nzbget releases |
| testing | ✅ | nzbget pre-releases |
## Application Setup
@ -83,7 +83,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
nzbget:
image: lscr.io/linuxserver/nzbget
image: lscr.io/linuxserver/nzbget:latest
container_name: nzbget
environment:
- PUID=1000
@ -113,7 +113,7 @@ docker run -d \
-v /path/to/data:/config \
-v /path/to/downloads:/downloads `#optional` \
--restart unless-stopped \
lscr.io/linuxserver/nzbget
lscr.io/linuxserver/nzbget:latest
```
## Parameters
@ -193,7 +193,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' nzbget`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/nzbget`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/nzbget:latest`
## Versions

32
images/docker-nzbhydra2.md
Wyświetl plik

@ -23,26 +23,26 @@ It provides easy access to a number of raw and newznab based indexers. The appli
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/nzbhydra2` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/nzbhydra2:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Version Tags
This image provides various versions that are available via tags. `latest` tag usually provides the latest stable version. Others are considered under development and caution must be exercised when using them.
This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.
| Tag | Description |
| :----: | --- |
| latest | Stable releases |
| dev | Prereleases from their GitHub |
| Tag | Available | Description |
| :----: | :----: |--- |
| latest | ✅ | Stable releases |
| dev | ✅ | Prereleases from their GitHub |
## Application Setup
@ -59,7 +59,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
nzbhydra2:
image: lscr.io/linuxserver/nzbhydra2
image: lscr.io/linuxserver/nzbhydra2:latest
container_name: nzbhydra2
environment:
- PUID=1000
@ -85,7 +85,7 @@ docker run -d \
-v <path to data>:/config \
-v <nzb download>:/downloads \
--restart unless-stopped \
lscr.io/linuxserver/nzbhydra2
lscr.io/linuxserver/nzbhydra2:latest
```
## Parameters
@ -163,10 +163,12 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' nzbhydra2`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/nzbhydra2`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/nzbhydra2:latest`
## Versions
* **03.05.22:** - Rebase to Jammy.
* **18.04.22:** - Rebase to Alpine 3.15.
* **01.05.20:** - Reorganize container, Relocate app to /app/nzbhydra2/bin, Create /app/nzbhydra2/package_info, Use nzbhydra2wrapperPy3.py from zip.
* **14.04.20:** - Correct Name, Hydra2 -> NZBHydra2.
* **08.01.20:** - Switch to python3.

31
images/docker-ombi.md
Wyświetl plik

@ -25,26 +25,26 @@ Even automatically send them weekly newsletters of new content that has been add
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/ombi` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/ombi:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Version Tags
This image provides various versions that are available via tags. `latest` tag usually provides the latest stable version. Others are considered under development and caution must be exercised when using them.
This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.
| Tag | Description |
| :----: | --- |
| latest | Stable Ombi releases |
| development | Releases from the `develop` branch of Ombi |
| Tag | Available | Description |
| :----: | :----: |--- |
| latest | ✅ | Stable Ombi releases |
| development | ✅ | Releases from the `develop` branch of Ombi |
## Application Setup
@ -61,7 +61,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
ombi:
image: lscr.io/linuxserver/ombi
image: lscr.io/linuxserver/ombi:latest
container_name: ombi
environment:
- PUID=1000
@ -87,7 +87,7 @@ docker run -d \
-p 3579:3579 \
-v /path/to/appdata/config:/config \
--restart unless-stopped \
lscr.io/linuxserver/ombi
lscr.io/linuxserver/ombi:latest
```
## Parameters
@ -165,10 +165,11 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' ombi`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/ombi`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/ombi:latest`
## Versions
* **01.05.22:** - Rebase to Jammy.
* **26.04.21:** - Update tarball name, allow for v4 builds in stable.
* **18.01.21:** - Update upstream repo. Deprecate `v4-preview` tag, which is merged to `development` tag upstream.
* **14.04.20:** - Add Ombi donate links.

21
images/docker-openssh-server.md
Wyświetl plik

@ -23,17 +23,17 @@ The users only have access to the folders mapped and the processes running insid
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/openssh-server` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/openssh-server:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -80,7 +80,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
openssh-server:
image: lscr.io/linuxserver/openssh-server
image: lscr.io/linuxserver/openssh-server:latest
container_name: openssh-server
hostname: openssh-server #optional
environment:
@ -124,7 +124,7 @@ docker run -d \
-p 2222:2222 \
-v /path/to/appdata/config:/config \
--restart unless-stopped \
lscr.io/linuxserver/openssh-server
lscr.io/linuxserver/openssh-server:latest
```
## Parameters
@ -211,10 +211,11 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' openssh-server`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/openssh-server`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/openssh-server:latest`
## Versions
* **16.04.22:** - Rebase to alpine 3.15.
* **16.11.21:** - Add PUBLIC_KEY_URL option
* **28.06.21:** - Rebasing to alpine 3.14. Add support for PAM.
* **10.02.21:** - Rebasing to alpine 3.13. Add openssh-client for scp.

30
images/docker-openvscode-server.md
Wyświetl plik

@ -21,26 +21,26 @@ title: openvscode-server
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/openvscode-server` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/openvscode-server:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Version Tags
This image provides various versions that are available via tags. `latest` tag usually provides the latest stable version. Others are considered under development and caution must be exercised when using them.
This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.
| Tag | Description |
| :----: | --- |
| latest | Stable releases |
| insiders | Insiders releases |
| Tag | Available | Description |
| :----: | :----: |--- |
| latest | ✅ | Stable releases |
| insiders | ✅ | Insiders releases |
## Application Setup
@ -67,7 +67,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
openvscode-server:
image: lscr.io/linuxserver/openvscode-server
image: lscr.io/linuxserver/openvscode-server:latest
container_name: openvscode-server
environment:
- PUID=1000
@ -99,7 +99,7 @@ docker run -d \
-p 3000:3000 \
-v /path/to/appdata/config:/config \
--restart unless-stopped \
lscr.io/linuxserver/openvscode-server
lscr.io/linuxserver/openvscode-server:latest
```
## Parameters
@ -180,7 +180,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' openvscode-server`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/openvscode-server`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/openvscode-server:latest`
## Versions

20
images/docker-oscam.md
Wyświetl plik

@ -21,17 +21,17 @@ title: oscam
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/oscam` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/oscam:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -49,7 +49,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
oscam:
image: lscr.io/linuxserver/oscam
image: lscr.io/linuxserver/oscam:latest
container_name: oscam
environment:
- PUID=1000
@ -76,7 +76,7 @@ docker run -d \
-v /path/to/data:/config \
--device /dev/ttyUSB0:/dev/ttyUSB0 \
--restart unless-stopped \
lscr.io/linuxserver/oscam
lscr.io/linuxserver/oscam:latest
```
### Passing through Smart Card Readers
@ -180,7 +180,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' oscam`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/oscam`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/oscam:latest`
## Versions

31
images/docker-overseerr.md
Wyświetl plik

@ -21,26 +21,26 @@ title: overseerr
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/overseerr` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/overseerr:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Version Tags
This image provides various versions that are available via tags. `latest` tag usually provides the latest stable version. Others are considered under development and caution must be exercised when using them.
This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.
| Tag | Description |
| :----: | --- |
| latest | Stable releases from GitHub |
| develop | Development releases from commits in upstream develop branch |
| Tag | Available | Description |
| :----: | :----: |--- |
| latest | ✅ | Stable releases from GitHub |
| develop | ✅ | Development releases from commits in upstream develop branch |
## Application Setup
@ -57,7 +57,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
overseerr:
image: lscr.io/linuxserver/overseerr
image: lscr.io/linuxserver/overseerr:latest
container_name: overseerr
environment:
- PUID=1000
@ -81,7 +81,7 @@ docker run -d \
-p 5055:5055 \
-v /path/to/appdata/config:/config \
--restart unless-stopped \
lscr.io/linuxserver/overseerr
lscr.io/linuxserver/overseerr:latest
```
## Parameters
@ -158,10 +158,11 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' overseerr`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/overseerr`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/overseerr:latest`
## Versions
* **01.04.22:** - Rebase main branch to Alpine 3.15.
* **27.01.22:** - Rebase develop branch to Alpine 3.15.
* **04.01.22:** - Remove cached files.
* **10.10.21:** - Add additional post-build cleanup.

20
images/docker-paperless-ng.md
Wyświetl plik

@ -21,17 +21,17 @@ title: paperless-ng
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/paperless-ng` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/paperless-ng:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -50,7 +50,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
paperless-ng:
image: lscr.io/linuxserver/paperless-ng
image: lscr.io/linuxserver/paperless-ng:latest
container_name: paperless-ng
environment:
- PUID=1000
@ -78,7 +78,7 @@ docker run -d \
-v </path/to/appdata/config>:/config \
-v </path/to/appdata/data>:/data \
--restart unless-stopped \
lscr.io/linuxserver/paperless-ng
lscr.io/linuxserver/paperless-ng:latest
```
## Parameters
@ -157,7 +157,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' paperless-ng`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/paperless-ng`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/paperless-ng:latest`
## Versions

37
images/docker-paperless-ngx.md
Wyświetl plik

@ -21,17 +21,17 @@ title: paperless-ngx
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/paperless-ngx` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/paperless-ngx:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -50,7 +50,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
paperless-ngx:
image: lscr.io/linuxserver/paperless-ngx
image: lscr.io/linuxserver/paperless-ngx:latest
container_name: paperless-ngx
environment:
- PUID=1000
@ -58,8 +58,8 @@ services:
- TZ=America/New_York
- REDIS_URL= #optional
volumes:
- </path/to/appdata/config>:/config
- </path/to/appdata/data>:/data
- /path/to/appdata/config:/config
- /path/to/appdata/data:/data
ports:
- 8000:8000
restart: unless-stopped
@ -75,10 +75,10 @@ docker run -d \
-e TZ=America/New_York \
-e REDIS_URL= `#optional` \
-p 8000:8000 \
-v </path/to/appdata/config>:/config \
-v </path/to/appdata/data>:/data \
-v /path/to/appdata/config:/config \
-v /path/to/appdata/data:/data \
--restart unless-stopped \
lscr.io/linuxserver/paperless-ngx
lscr.io/linuxserver/paperless-ngx:latest
```
## Parameters
@ -157,8 +157,17 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' paperless-ngx`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/paperless-ngx`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/paperless-ngx:latest`
## Versions
* **16.05.22:** - Add correct libqpdf.so to arm builds.
* **14.05.22:** - Fine tune disabling of redis.
* **12.05.22:** - Move migrations to after multilangocr mod. Fix disabling of redis. Add missing dep for postgresql.
* **12.05.22:** - Utilize lsio wheel for pikepdf.
* **11.05.22:** - Update upstream artifact name and utilize lsio wheels for scipy and scikit-learn.
* **05.05.22:** - Add runtime dependencies libxslt1.1 for armhf
* **30.04.22:** - Add runtime dependencies lizbar and poppler-utils
* **27.04.22:** - Add build-dependencies for arm32 builds.
* **11.04.22:** - Replaced uwsgi with gunicorn due to websocket issues.
* **11.03.22:** - Initial Release.

20
images/docker-papermerge.md
Wyświetl plik

@ -21,17 +21,17 @@ title: papermerge
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/papermerge` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/papermerge:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -51,7 +51,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
papermerge:
image: lscr.io/linuxserver/papermerge
image: lscr.io/linuxserver/papermerge:latest
container_name: papermerge
environment:
- PUID=1000
@ -79,7 +79,7 @@ docker run -d \
-v </path/to/appdata/config>:/config \
-v </path/to/appdata/data>:/data \
--restart unless-stopped \
lscr.io/linuxserver/papermerge
lscr.io/linuxserver/papermerge:latest
```
## Parameters
@ -158,7 +158,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' papermerge`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/papermerge`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/papermerge:latest`
## Versions

20
images/docker-photoshow.md
Wyświetl plik

@ -21,17 +21,17 @@ title: photoshow
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/photoshow` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/photoshow:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -48,7 +48,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
photoshow:
image: lscr.io/linuxserver/photoshow
image: lscr.io/linuxserver/photoshow:latest
container_name: photoshow
environment:
- PUID=1000
@ -76,7 +76,7 @@ docker run -d \
-v <path to pictures>:/Pictures:ro \
-v <path to store thumbs>:/Thumbs \
--restart unless-stopped \
lscr.io/linuxserver/photoshow
lscr.io/linuxserver/photoshow:latest
```
## Parameters
@ -155,7 +155,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' photoshow`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/photoshow`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/photoshow:latest`
## Versions

20
images/docker-phpmyadmin.md
Wyświetl plik

@ -21,17 +21,17 @@ title: phpmyadmin
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/phpmyadmin` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/phpmyadmin:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -52,7 +52,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
phpmyadmin:
image: lscr.io/linuxserver/phpmyadmin
image: lscr.io/linuxserver/phpmyadmin:latest
container_name: phpmyadmin
environment:
- PUID=1000
@ -80,7 +80,7 @@ docker run -d \
-p 80:80 \
-v /path/to/appdata/config:/config \
--restart unless-stopped \
lscr.io/linuxserver/phpmyadmin
lscr.io/linuxserver/phpmyadmin:latest
```
## Parameters
@ -159,7 +159,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' phpmyadmin`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/phpmyadmin`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/phpmyadmin:latest`
## Versions

20
images/docker-pidgin.md
Wyświetl plik

@ -21,17 +21,17 @@ title: pidgin
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/pidgin` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/pidgin:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -75,7 +75,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
pidgin:
image: lscr.io/linuxserver/pidgin
image: lscr.io/linuxserver/pidgin:latest
container_name: pidgin
environment:
- PUID=1000
@ -99,7 +99,7 @@ docker run -d \
-p 3000:3000 \
-v /path/to/config:/config \
--restart unless-stopped \
lscr.io/linuxserver/pidgin
lscr.io/linuxserver/pidgin:latest
```
## Parameters
@ -176,7 +176,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' pidgin`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/pidgin`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/pidgin:latest`
## Versions

20
images/docker-piwigo.md
Wyświetl plik

@ -21,17 +21,17 @@ title: piwigo
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/piwigo` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/piwigo:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -53,7 +53,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
piwigo:
image: lscr.io/linuxserver/piwigo
image: lscr.io/linuxserver/piwigo:latest
container_name: piwigo
environment:
- PUID=1000
@ -79,7 +79,7 @@ docker run -d \
-v </path/to/appdata/config>:/config \
-v </path/to/appdata/gallery>:/gallery \
--restart unless-stopped \
lscr.io/linuxserver/piwigo
lscr.io/linuxserver/piwigo:latest
```
## Parameters
@ -157,7 +157,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' piwigo`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/piwigo`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/piwigo:latest`
## Versions

20
images/docker-pixapop.md
Wyświetl plik

@ -21,17 +21,17 @@ title: pixapop
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/pixapop` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/pixapop:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -48,7 +48,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
pixapop:
image: lscr.io/linuxserver/pixapop
image: lscr.io/linuxserver/pixapop:latest
container_name: pixapop
environment:
- PUID=1000
@ -78,7 +78,7 @@ docker run -d \
-v /path/to/config:/config \
-v /path/to/photos:/photos \
--restart unless-stopped \
lscr.io/linuxserver/pixapop
lscr.io/linuxserver/pixapop:latest
```
## Parameters
@ -158,7 +158,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' pixapop`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/pixapop`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/pixapop:latest`
## Versions

20
images/docker-plex-meta-manager.md
Wyświetl plik

@ -21,17 +21,17 @@ title: plex-meta-manager
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/plex-meta-manager` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/plex-meta-manager:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Application Setup
@ -52,7 +52,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
plex-meta-manager:
image: lscr.io/linuxserver/plex-meta-manager
image: lscr.io/linuxserver/plex-meta-manager:latest
container_name: plex-meta-manager
environment:
- PUID=1000
@ -83,7 +83,7 @@ docker run -d \
-e PMM_NO_MISSING=False `#optional` \
-v /path/to/appdata/config:/config \
--restart unless-stopped \
lscr.io/linuxserver/plex-meta-manager
lscr.io/linuxserver/plex-meta-manager:latest
```
## Parameters
@ -164,7 +164,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' plex-meta-manager`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/plex-meta-manager`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/plex-meta-manager:latest`
## Versions

31
images/docker-plex.md
Wyświetl plik

@ -21,26 +21,26 @@ title: plex
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `lscr.io/linuxserver/plex` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
Simply pulling `lscr.io/linuxserver/plex:latest` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v7-latest |
| Architecture | Available | Tag |
| :----: | :----: | ---- |
| x86-64 | ✅ | amd64-\<version tag\> |
| arm64 | ✅ | arm64v8-\<version tag\> |
| armhf| ✅ | arm32v7-\<version tag\> |
## Version Tags
This image provides various versions that are available via tags. `latest` tag usually provides the latest stable version. Others are considered under development and caution must be exercised when using them.
This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.
| Tag | Description |
| :----: | --- |
| latest | Stable releases with Focal baseimage |
| bionic | DEPRECATED - Stable releases with Bionic baseimage |
| Tag | Available | Description |
| :----: | :----: |--- |
| latest | ✅ | Stable releases with Focal baseimage |
| bionic | ✅ | DEPRECATED - Stable releases with Bionic baseimage |
## Application Setup
@ -90,7 +90,7 @@ To help you get started creating a container from this image you can either use
version: "2.1"
services:
plex:
image: lscr.io/linuxserver/plex
image: lscr.io/linuxserver/plex:latest
container_name: plex
network_mode: host
environment:
@ -119,7 +119,7 @@ docker run -d \
-v /path/to/tvseries:/tv \
-v /path/to/movies:/movies \
--restart unless-stopped \
lscr.io/linuxserver/plex
lscr.io/linuxserver/plex:latest
```
## Parameters
@ -232,10 +232,11 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' plex`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/plex`
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/plex:latest`
## Versions
* **16.05.22:** - Pin opencl version.
* **04.03.22:** - Increase verbosity of video device permissions fix, attempt to fix missing group rw.
* **25.12.21:** - Install Intel drivers from the official repo.
* **20.01.21:** - Deprecate `UMASK_SET` in favor of UMASK in baseimage, see above for more information.

Some files were not shown because too many files have changed in this diff Show More