diff --git a/FAQ.md b/FAQ.md index 84fdd2738..9458cf645 100644 --- a/FAQ.md +++ b/FAQ.md @@ -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. diff --git a/general/awesome-lsio.md b/general/awesome-lsio.md index b425cff5b..5a6c2dfe8 100644 --- a/general/awesome-lsio.md +++ b/general/awesome-lsio.md @@ -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. | diff --git a/general/docker-compose.md b/general/docker-compose.md index af422ffd0..48d8263b8 100644 --- a/general/docker-compose.md +++ b/general/docker-compose.md @@ -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 ` 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: diff --git a/images/docker-adguardhome-sync.md b/images/docker-adguardhome-sync.md index 70804e828..f5a50977f 100755 --- a/images/docker-adguardhome-sync.md +++ b/images/docker-adguardhome-sync.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 diff --git a/images/docker-airsonic-advanced.md b/images/docker-airsonic-advanced.md index 0644dc9c3..94440524d 100755 --- a/images/docker-airsonic-advanced.md +++ b/images/docker-airsonic-advanced.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| 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 :/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 diff --git a/images/docker-apprise-api.md b/images/docker-apprise-api.md index 754041dcf..24d1917e5 100755 --- a/images/docker-apprise-api.md +++ b/images/docker-apprise-api.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | + ## 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 diff --git a/images/docker-audacity.md b/images/docker-audacity.md index 7c82a7327..4623f1db3 100755 --- a/images/docker-audacity.md +++ b/images/docker-audacity.md @@ -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-\ | +| 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 diff --git a/images/docker-babybuddy.md b/images/docker-babybuddy.md index a99aa3b1a..b47f8a1a8 100755 --- a/images/docker-babybuddy.md +++ b/images/docker-babybuddy.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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. diff --git a/images/docker-bazarr.md b/images/docker-bazarr.md index de3b1d17d..770cc5329 100644 --- a/images/docker-bazarr.md +++ b/images/docker-bazarr.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 diff --git a/images/docker-beets.md b/images/docker-beets.md index 5fecc34c5..be9caf89d 100644 --- a/images/docker-beets.md +++ b/images/docker-beets.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 :/music \ -v :/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 diff --git a/images/docker-blender.md b/images/docker-blender.md index a20657500..71ddab9ff 100755 --- a/images/docker-blender.md +++ b/images/docker-blender.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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. diff --git a/images/docker-boinc.md b/images/docker-boinc.md index f39e08074..1ee0fc660 100644 --- a/images/docker-boinc.md +++ b/images/docker-boinc.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 diff --git a/images/docker-booksonic-air.md b/images/docker-booksonic-air.md index 5b28c2a8c..bf2a3faaa 100755 --- a/images/docker-booksonic-air.md +++ b/images/docker-booksonic-air.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 :/podcasts \ -v :/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. diff --git a/images/docker-bookstack.md b/images/docker-bookstack.md index bbd6da92e..3ec3a8ba6 100644 --- a/images/docker-bookstack.md +++ b/images/docker-bookstack.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 diff --git a/images/docker-budge.md b/images/docker-budge.md index e92910393..c00cb2a41 100755 --- a/images/docker-budge.md +++ b/images/docker-budge.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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. diff --git a/images/docker-calibre-web.md b/images/docker-calibre-web.md index a2226e03c..641273aae 100644 --- a/images/docker-calibre-web.md +++ b/images/docker-calibre-web.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 diff --git a/images/docker-calibre.md b/images/docker-calibre.md index d9fae33a9..21c17d76a 100644 --- a/images/docker-calibre.md +++ b/images/docker-calibre.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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. diff --git a/images/docker-chevereto.md b/images/docker-chevereto.md index a1266767d..089b3a98e 100755 --- a/images/docker-chevereto.md +++ b/images/docker-chevereto.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## Application Setup @@ -102,7 +102,7 @@ docker run -d \ -v :/config \ -v :/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 diff --git a/images/docker-cloud9.md b/images/docker-cloud9.md index c623b5ce0..8176e92c6 100644 --- a/images/docker-cloud9.md +++ b/images/docker-cloud9.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 diff --git a/images/docker-code-server.md b/images/docker-code-server.md index d2294db73..52cb40e1f 100644 --- a/images/docker-code-server.md +++ b/images/docker-code-server.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 diff --git a/images/docker-cops.md b/images/docker-cops.md index c65fe66ed..a9bdf310a 100644 --- a/images/docker-cops.md +++ b/images/docker-cops.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 :/config \ -v :/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 diff --git a/images/docker-daapd.md b/images/docker-daapd.md index 75fbbc9ad..89af479f0 100644 --- a/images/docker-daapd.md +++ b/images/docker-daapd.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 :/config \ -v :/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 diff --git a/images/docker-darktable.md b/images/docker-darktable.md index 78850ebe6..ea28a4460 100755 --- a/images/docker-darktable.md +++ b/images/docker-darktable.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| 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 diff --git a/images/docker-davos.md b/images/docker-davos.md index 7b874140b..d066d7827 100644 --- a/images/docker-davos.md +++ b/images/docker-davos.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 :/config \ -v :/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 diff --git a/images/docker-ddclient.md b/images/docker-ddclient.md index cf45f4133..638c428d2 100644 --- a/images/docker-ddclient.md +++ b/images/docker-ddclient.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 :/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 diff --git a/images/docker-deluge.md b/images/docker-deluge.md index 954a6fee3..a7f859fb5 100644 --- a/images/docker-deluge.md +++ b/images/docker-deluge.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 diff --git a/images/docker-digikam.md b/images/docker-digikam.md index 91c2293b4..ffb55eb7d 100644 --- a/images/docker-digikam.md +++ b/images/docker-digikam.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 diff --git a/images/docker-dillinger.md b/images/docker-dillinger.md index b37b9c514..4385b1a4f 100644 --- a/images/docker-dillinger.md +++ b/images/docker-dillinger.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| 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 :/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. diff --git a/images/docker-diskover.md b/images/docker-diskover.md index 51b40a355..ac103349c 100644 --- a/images/docker-diskover.md +++ b/images/docker-diskover.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 diff --git a/images/docker-docker-compose.md b/images/docker-docker-compose.md index f521d359e..aeca62fec 100755 --- a/images/docker-docker-compose.md +++ b/images/docker-docker-compose.md @@ -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 diff --git a/images/docker-dokuwiki.md b/images/docker-dokuwiki.md index 9f4ca8548..3fc6c16ca 100644 --- a/images/docker-dokuwiki.md +++ b/images/docker-dokuwiki.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 diff --git a/images/docker-domoticz.md b/images/docker-domoticz.md index 4504fcb5a..18656dd38 100644 --- a/images/docker-domoticz.md +++ b/images/docker-domoticz.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 :/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 diff --git a/images/docker-doplarr.md b/images/docker-doplarr.md index 3e1de810a..4b3af0bd6 100755 --- a/images/docker-doplarr.md +++ b/images/docker-doplarr.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| 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__URL=http://localhost:8989 - DISCORD__MAX_RESULTS=25 #optional - - DISCORD__ROLE_ID= #optional - DISCORD__REQUESTED_MSG_STYLE=:plain #optional - SONARR__QUALITY_PROFILE= #optional - RADARR__QUALITY_PROFILE= #optional + - SONARR__ROOTFOLDER= #optional + - RADARR__ROOTFOLDER= #optional - SONARR__LANGUAGE_PROFILE= #optional - OVERSEERR__DEFAULT_ID= #optional - PARTIAL_SEASONS=true #optional @@ -100,10 +102,11 @@ docker run -d \ -e SONARR__API= \ -e SONARR__URL=http://localhost:8989 \ -e DISCORD__MAX_RESULTS=25 `#optional` \ - -e DISCORD__ROLE_ID= `#optional` \ -e DISCORD__REQUESTED_MSG_STYLE=:plain `#optional` \ -e SONARR__QUALITY_PROFILE= `#optional` \ -e RADARR__QUALITY_PROFILE= `#optional` \ + -e SONARR__ROOTFOLDER= `#optional` \ + -e RADARR__ROOTFOLDER= `#optional` \ -e SONARR__LANGUAGE_PROFILE= `#optional` \ -e OVERSEERR__DEFAULT_ID= `#optional` \ -e PARTIAL_SEASONS=true `#optional` \ @@ -111,7 +114,7 @@ docker run -d \ -e JAVA_OPTS= `#optional` \ -v :/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=` | 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=` | 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=` | The name of the quality profile to use by default for Sonarr | | `RADARR__QUALITY_PROFILE=` | The name of the quality profile to use by default for Radarr | -| `SONARR__LANGUAGE_PROFILE=` | The name of the language profile to use by default for Radarr | +| `SONARR__ROOTFOLDER=` | The root folder to use by default for Sonarr | +| `RADARR__ROOTFOLDER=` | The root folder to use by default for Radarr | +| `SONARR__LANGUAGE_PROFILE=` | The name of the language profile to use by default for Sonarr | | `OVERSEERR__DEFAULT_ID=` | 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. diff --git a/images/docker-doublecommander.md b/images/docker-doublecommander.md index 9d8704f2b..b7d1a144d 100644 --- a/images/docker-doublecommander.md +++ b/images/docker-doublecommander.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 diff --git a/images/docker-duckdns.md b/images/docker-duckdns.md index ec72d4828..75275a159 100644 --- a/images/docker-duckdns.md +++ b/images/docker-duckdns.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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. diff --git a/images/docker-duplicati.md b/images/docker-duplicati.md index 5f2c3f271..d429a5f33 100644 --- a/images/docker-duplicati.md +++ b/images/docker-duplicati.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 :/backups \ -v :/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. diff --git a/images/docker-emby.md b/images/docker-emby.md index 45967a103..0e60b9cea 100644 --- a/images/docker-emby.md +++ b/images/docker-emby.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 diff --git a/images/docker-embystat.md b/images/docker-embystat.md index 8b1eeda37..5ecadd5b0 100644 --- a/images/docker-embystat.md +++ b/images/docker-embystat.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 diff --git a/images/docker-emulatorjs.md b/images/docker-emulatorjs.md index 7b24bef0c..73e5fded9 100755 --- a/images/docker-emulatorjs.md +++ b/images/docker-emulatorjs.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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. diff --git a/images/docker-endlessh.md b/images/docker-endlessh.md index e592766d9..eed7e80e5 100755 --- a/images/docker-endlessh.md +++ b/images/docker-endlessh.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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. diff --git a/images/docker-filezilla.md b/images/docker-filezilla.md index dbb00cf79..afbeb4d83 100755 --- a/images/docker-filezilla.md +++ b/images/docker-filezilla.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 diff --git a/images/docker-firefox.md b/images/docker-firefox.md index 96fe09694..47219312a 100755 --- a/images/docker-firefox.md +++ b/images/docker-firefox.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 diff --git a/images/docker-fleet.md b/images/docker-fleet.md index 104bc62ea..05f39c52f 100644 --- a/images/docker-fleet.md +++ b/images/docker-fleet.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 :/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. diff --git a/images/docker-foldingathome.md b/images/docker-foldingathome.md index 754e3372c..76b231442 100644 --- a/images/docker-foldingathome.md +++ b/images/docker-foldingathome.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| 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 diff --git a/images/docker-freshrss.md b/images/docker-freshrss.md index 216d7a24d..076a64614 100644 --- a/images/docker-freshrss.md +++ b/images/docker-freshrss.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 diff --git a/images/docker-gmail-order-bot.md b/images/docker-gmail-order-bot.md index 72143d9ee..46711713b 100755 --- a/images/docker-gmail-order-bot.md +++ b/images/docker-gmail-order-bot.md @@ -1,129 +1,36 @@ -# [lsiodev/gmail-order-bot](https://github.com/linuxserver/docker-gmail-order-bot) +--- +title: gmail-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/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 `:` 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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 `:` 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 diff --git a/images/docker-grav.md b/images/docker-grav.md index 4bbacc92a..72144f1e0 100755 --- a/images/docker-grav.md +++ b/images/docker-grav.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 diff --git a/images/docker-grocy.md b/images/docker-grocy.md index 51f9ece32..b9ab90b21 100644 --- a/images/docker-grocy.md +++ b/images/docker-grocy.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 diff --git a/images/docker-guacd.md b/images/docker-guacd.md index 4ed2a3142..a158ab888 100644 --- a/images/docker-guacd.md +++ b/images/docker-guacd.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 diff --git a/images/docker-headphones.md b/images/docker-headphones.md index f92098592..1ef236ca3 100644 --- a/images/docker-headphones.md +++ b/images/docker-headphones.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | + ## 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 :/downloads \ -v :/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 diff --git a/images/docker-healthchecks.md b/images/docker-healthchecks.md index 5baa1cc13..3be906a60 100644 --- a/images/docker-healthchecks.md +++ b/images/docker-healthchecks.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 :/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 diff --git a/images/docker-hedgedoc.md b/images/docker-hedgedoc.md index b2ecbdd62..13e50e38a 100755 --- a/images/docker-hedgedoc.md +++ b/images/docker-hedgedoc.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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. diff --git a/images/docker-heimdall.md b/images/docker-heimdall.md index 4f2f2840e..cc8b8860a 100644 --- a/images/docker-heimdall.md +++ b/images/docker-heimdall.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 :/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 diff --git a/images/docker-homeassistant.md b/images/docker-homeassistant.md index 991e0c95f..4479f2f56 100755 --- a/images/docker-homeassistant.md +++ b/images/docker-homeassistant.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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. diff --git a/images/docker-htpcmanager.md b/images/docker-htpcmanager.md index 350064204..742d5852c 100644 --- a/images/docker-htpcmanager.md +++ b/images/docker-htpcmanager.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 diff --git a/images/docker-jackett.md b/images/docker-jackett.md index dc8a565d3..ca0481e11 100644 --- a/images/docker-jackett.md +++ b/images/docker-jackett.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 :/config \ -v :/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. diff --git a/images/docker-jellyfin.md b/images/docker-jellyfin.md index 5b72bc629..afc0f6a36 100644 --- a/images/docker-jellyfin.md +++ b/images/docker-jellyfin.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 diff --git a/images/docker-jenkins-builder.md b/images/docker-jenkins-builder.md index e9f657148..bf846c5a6 100755 --- a/images/docker-jenkins-builder.md +++ b/images/docker-jenkins-builder.md @@ -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 ``` diff --git a/images/docker-kanzi.md b/images/docker-kanzi.md index 435993b88..54a5927be 100644 --- a/images/docker-kanzi.md +++ b/images/docker-kanzi.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 :/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 diff --git a/images/docker-kdenlive.md b/images/docker-kdenlive.md index 52acb3c0b..f5d13a7a8 100755 --- a/images/docker-kdenlive.md +++ b/images/docker-kdenlive.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 diff --git a/images/docker-lazylibrarian.md b/images/docker-lazylibrarian.md index 09ce1e3a6..aa12277d7 100644 --- a/images/docker-lazylibrarian.md +++ b/images/docker-lazylibrarian.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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. diff --git a/images/docker-ldap-auth.md b/images/docker-ldap-auth.md index faf7aa239..1fbeacb26 100644 --- a/images/docker-ldap-auth.md +++ b/images/docker-ldap-auth.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 diff --git a/images/docker-libreoffice.md b/images/docker-libreoffice.md index 2416531e7..d48d0eaa9 100755 --- a/images/docker-libreoffice.md +++ b/images/docker-libreoffice.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 diff --git a/images/docker-librespeed.md b/images/docker-librespeed.md index ca63432b7..2caadd93b 100644 --- a/images/docker-librespeed.md +++ b/images/docker-librespeed.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 diff --git a/images/docker-lidarr.md b/images/docker-lidarr.md index 96fa0804c..1b3e0dbcf 100644 --- a/images/docker-lidarr.md +++ b/images/docker-lidarr.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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. diff --git a/images/docker-limnoria.md b/images/docker-limnoria.md index 210288269..5247f8491 100644 --- a/images/docker-limnoria.md +++ b/images/docker-limnoria.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 diff --git a/images/docker-lychee.md b/images/docker-lychee.md index 2ce3c953b..f80faa24d 100644 --- a/images/docker-lychee.md +++ b/images/docker-lychee.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 diff --git a/images/docker-mariadb.md b/images/docker-mariadb.md index 113be5ef1..1558a4f2c 100644 --- a/images/docker-mariadb.md +++ b/images/docker-mariadb.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 diff --git a/images/docker-medusa.md b/images/docker-medusa.md index ea860f4a9..efba9074b 100644 --- a/images/docker-medusa.md +++ b/images/docker-medusa.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 :/downloads \ -v :/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 diff --git a/images/docker-minetest.md b/images/docker-minetest.md index 9feddc894..3465f356a 100644 --- a/images/docker-minetest.md +++ b/images/docker-minetest.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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. diff --git a/images/docker-minisatip.md b/images/docker-minisatip.md index b9d3cafde..a108e5125 100644 --- a/images/docker-minisatip.md +++ b/images/docker-minisatip.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 :/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 diff --git a/images/docker-mstream.md b/images/docker-mstream.md index cae16d2d4..6443982aa 100644 --- a/images/docker-mstream.md +++ b/images/docker-mstream.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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. diff --git a/images/docker-muximux.md b/images/docker-muximux.md index 2b7efdc48..2f15f0ee9 100644 --- a/images/docker-muximux.md +++ b/images/docker-muximux.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 :/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 diff --git a/images/docker-mylar3.md b/images/docker-mylar3.md index 2aa38bc59..66d70c46f 100755 --- a/images/docker-mylar3.md +++ b/images/docker-mylar3.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 diff --git a/images/docker-mysql-workbench.md b/images/docker-mysql-workbench.md index bfac14a79..4e0ee9622 100644 --- a/images/docker-mysql-workbench.md +++ b/images/docker-mysql-workbench.md @@ -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-\ | +| 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 diff --git a/images/docker-nano-wallet.md b/images/docker-nano-wallet.md index a8707b251..c14dafc77 100644 --- a/images/docker-nano-wallet.md +++ b/images/docker-nano-wallet.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 diff --git a/images/docker-nano.md b/images/docker-nano.md index 17f0aaec0..82998ba67 100644 --- a/images/docker-nano.md +++ b/images/docker-nano.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| 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 diff --git a/images/docker-netbootxyz.md b/images/docker-netbootxyz.md index a3f69fe20..66e750cf4 100644 --- a/images/docker-netbootxyz.md +++ b/images/docker-netbootxyz.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 diff --git a/images/docker-netbox.md b/images/docker-netbox.md index afeebb25e..1d8789cc6 100755 --- a/images/docker-netbox.md +++ b/images/docker-netbox.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 :/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. diff --git a/images/docker-nextcloud.md b/images/docker-nextcloud.md index 873391b21..25c847a14 100644 --- a/images/docker-nextcloud.md +++ b/images/docker-nextcloud.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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). diff --git a/images/docker-nginx.md b/images/docker-nginx.md index 26edd447b..6716ea055 100644 --- a/images/docker-nginx.md +++ b/images/docker-nginx.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 :/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 diff --git a/images/docker-ngircd.md b/images/docker-ngircd.md index 4057c5aa8..ce2f4a0bf 100644 --- a/images/docker-ngircd.md +++ b/images/docker-ngircd.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 :/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 diff --git a/images/docker-nntp2nntp.md b/images/docker-nntp2nntp.md index 30db16f8c..1fe24b81b 100644 --- a/images/docker-nntp2nntp.md +++ b/images/docker-nntp2nntp.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 :/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 diff --git a/images/docker-nzbget.md b/images/docker-nzbget.md index 98cb340fb..a227b6f11 100644 --- a/images/docker-nzbget.md +++ b/images/docker-nzbget.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 diff --git a/images/docker-nzbhydra2.md b/images/docker-nzbhydra2.md index 130e3da22..8a65976b0 100644 --- a/images/docker-nzbhydra2.md +++ b/images/docker-nzbhydra2.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 :/config \ -v :/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. diff --git a/images/docker-ombi.md b/images/docker-ombi.md index 6b4adcf5b..9832dab2a 100644 --- a/images/docker-ombi.md +++ b/images/docker-ombi.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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. diff --git a/images/docker-openssh-server.md b/images/docker-openssh-server.md index 49d1ffed1..60f0b6811 100644 --- a/images/docker-openssh-server.md +++ b/images/docker-openssh-server.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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. diff --git a/images/docker-openvscode-server.md b/images/docker-openvscode-server.md index c3e76fc41..e8b88c76b 100755 --- a/images/docker-openvscode-server.md +++ b/images/docker-openvscode-server.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 diff --git a/images/docker-oscam.md b/images/docker-oscam.md index 4e9772771..70c4e4b57 100644 --- a/images/docker-oscam.md +++ b/images/docker-oscam.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 diff --git a/images/docker-overseerr.md b/images/docker-overseerr.md index 852daf719..fff95818a 100755 --- a/images/docker-overseerr.md +++ b/images/docker-overseerr.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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. diff --git a/images/docker-paperless-ng.md b/images/docker-paperless-ng.md index 6e40050c5..0c5c441f1 100755 --- a/images/docker-paperless-ng.md +++ b/images/docker-paperless-ng.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 :/config \ -v :/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 diff --git a/images/docker-paperless-ngx.md b/images/docker-paperless-ngx.md index 0f8136dd1..ebea59ebe 100755 --- a/images/docker-paperless-ngx.md +++ b/images/docker-paperless-ngx.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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: - - :/config - - :/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 :/config \ - -v :/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. diff --git a/images/docker-papermerge.md b/images/docker-papermerge.md index a8092f3c2..575b89d2b 100755 --- a/images/docker-papermerge.md +++ b/images/docker-papermerge.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 :/config \ -v :/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 diff --git a/images/docker-photoshow.md b/images/docker-photoshow.md index aab65dcf7..3b20880ea 100644 --- a/images/docker-photoshow.md +++ b/images/docker-photoshow.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 :/Pictures:ro \ -v :/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 diff --git a/images/docker-phpmyadmin.md b/images/docker-phpmyadmin.md index ae11858e4..cf2a7c2c8 100755 --- a/images/docker-phpmyadmin.md +++ b/images/docker-phpmyadmin.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 diff --git a/images/docker-pidgin.md b/images/docker-pidgin.md index 1a8ce96f8..83f46928a 100755 --- a/images/docker-pidgin.md +++ b/images/docker-pidgin.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 diff --git a/images/docker-piwigo.md b/images/docker-piwigo.md index 65c2f212b..cd930479e 100644 --- a/images/docker-piwigo.md +++ b/images/docker-piwigo.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 :/config \ -v :/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 diff --git a/images/docker-pixapop.md b/images/docker-pixapop.md index f9fd85e21..462598031 100644 --- a/images/docker-pixapop.md +++ b/images/docker-pixapop.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 diff --git a/images/docker-plex-meta-manager.md b/images/docker-plex-meta-manager.md index cf5e36a47..9232d21ba 100755 --- a/images/docker-plex-meta-manager.md +++ b/images/docker-plex-meta-manager.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 diff --git a/images/docker-plex.md b/images/docker-plex.md index bd63d98a2..d3232cc6b 100644 --- a/images/docker-plex.md +++ b/images/docker-plex.md @@ -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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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. diff --git a/images/docker-projectsend.md b/images/docker-projectsend.md index bb5bd0c92..d8bdf2519 100644 --- a/images/docker-projectsend.md +++ b/images/docker-projectsend.md @@ -21,17 +21,17 @@ title: projectsend ## 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/projectsend` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/projectsend: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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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: projectsend: - image: lscr.io/linuxserver/projectsend + image: lscr.io/linuxserver/projectsend:latest container_name: projectsend environment: - PUID=1000 @@ -80,7 +80,7 @@ docker run -d \ -v :/config \ -v :/data \ --restart unless-stopped \ - lscr.io/linuxserver/projectsend + lscr.io/linuxserver/projectsend: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" }}' projectsend` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/projectsend` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/projectsend:latest` ## Versions diff --git a/images/docker-pwndrop.md b/images/docker-pwndrop.md index 792599954..4e32edb1c 100644 --- a/images/docker-pwndrop.md +++ b/images/docker-pwndrop.md @@ -21,17 +21,17 @@ title: pwndrop ## 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/pwndrop` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/pwndrop: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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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: pwndrop: - image: lscr.io/linuxserver/pwndrop + image: lscr.io/linuxserver/pwndrop:latest container_name: pwndrop environment: - PUID=1000 @@ -74,7 +74,7 @@ docker run -d \ -p 8080:8080 \ -v /path/to/appdata:/config \ --restart unless-stopped \ - lscr.io/linuxserver/pwndrop + lscr.io/linuxserver/pwndrop: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" }}' pwndrop` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/pwndrop` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/pwndrop:latest` ## Versions diff --git a/images/docker-pydio-cells.md b/images/docker-pydio-cells.md index 4a69bb7fe..799cfd5a0 100644 --- a/images/docker-pydio-cells.md +++ b/images/docker-pydio-cells.md @@ -23,13 +23,15 @@ title: pydio-cells 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/pydio-cells` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/pydio-cells: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 | +| Architecture | Available | Tag | +| :----: | :----: | ---- | +| x86-64 | ✅ | amd64-\ | +| arm64 | ❌ | | +| armhf| ❌ | | ## Application Setup @@ -37,6 +39,11 @@ You must first create a mysql database for Pydio Cells. Using our [mariadb image Then access the web gui setup wizard at `https://SERVER_IP:8080` if accessing locally (must set `SERVER_IP` env var), or at `https://pydio-cells.domain.com` if reverse proxying. +### 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. @@ -48,7 +55,7 @@ To help you get started creating a container from this image you can either use version: "2.1" services: pydio-cells: - image: lscr.io/linuxserver/pydio-cells + image: lscr.io/linuxserver/pydio-cells:latest container_name: pydio-cells hostname: pydio-cells environment: @@ -80,7 +87,7 @@ docker run -d \ -p 33060:33060 `#optional` \ -v /path/to/appdata/config:/config \ --restart unless-stopped \ - lscr.io/linuxserver/pydio-cells + lscr.io/linuxserver/pydio-cells:latest ``` ## Parameters @@ -161,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" }}' pydio-cells` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/pydio-cells` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/pydio-cells:latest` ## Versions diff --git a/images/docker-pyload-ng.md b/images/docker-pyload-ng.md index 872319a4b..0d213434e 100755 --- a/images/docker-pyload-ng.md +++ b/images/docker-pyload-ng.md @@ -21,26 +21,26 @@ title: pyload-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/pyload-ng` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/pyload-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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 pyLoad Next | -| develop | Releases from pyload Next develop branch | +| Tag | Available | Description | +| :----: | :----: |--- | +| latest | ✅ | Stable releases from pyLoad Next | +| develop | ✅ | Releases from pyload Next develop branch | ## 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: pyload-ng: - image: lscr.io/linuxserver/pyload-ng + image: lscr.io/linuxserver/pyload-ng:latest container_name: pyload-ng environment: - PUID=1000 @@ -89,7 +89,7 @@ docker run -d \ -v /path/to/appdata/config:/config \ -v /path/to/downloads:/downloads \ --restart unless-stopped \ - lscr.io/linuxserver/pyload-ng + lscr.io/linuxserver/pyload-ng: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" }}' pyload-ng` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/pyload-ng` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/pyload-ng:latest` ## Versions diff --git a/images/docker-pylon.md b/images/docker-pylon.md index 9ede59d56..8e6c0a86e 100644 --- a/images/docker-pylon.md +++ b/images/docker-pylon.md @@ -21,17 +21,17 @@ title: pylon ## 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/pylon` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/pylon: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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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: pylon: - image: lscr.io/linuxserver/pylon + image: lscr.io/linuxserver/pylon:latest container_name: pylon environment: - PUID=1000 @@ -78,7 +78,7 @@ docker run -d \ -p 3131:3131 \ -v :/code `#optional` \ --restart unless-stopped \ - lscr.io/linuxserver/pylon + lscr.io/linuxserver/pylon: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" }}' pylon` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/pylon` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/pylon:latest` ## Versions diff --git a/images/docker-qbittorrent.md b/images/docker-qbittorrent.md index 4e4eabc3d..9ab249979 100644 --- a/images/docker-qbittorrent.md +++ b/images/docker-qbittorrent.md @@ -21,25 +21,25 @@ The [Qbittorrent](https://www.qbittorrent.org/) project aims to provide an open- ## 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/qbittorrent` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/qbittorrent: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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 qbittorrent releases | +| Tag | Available | Description | +| :----: | :----: |--- | +| latest | ✅ | Stable qbittorrent releases | ## 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: qbittorrent: - image: lscr.io/linuxserver/qbittorrent + image: lscr.io/linuxserver/qbittorrent:latest container_name: qbittorrent environment: - PUID=1000 @@ -111,7 +111,7 @@ docker run -d \ -v /path/to/appdata/config:/config \ -v /path/to/downloads:/downloads \ --restart unless-stopped \ - lscr.io/linuxserver/qbittorrent + lscr.io/linuxserver/qbittorrent:latest ``` ## Parameters @@ -192,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" }}' qbittorrent` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/qbittorrent` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/qbittorrent:latest` ## Versions diff --git a/images/docker-qdirstat.md b/images/docker-qdirstat.md index f6a365f73..6b6393918 100755 --- a/images/docker-qdirstat.md +++ b/images/docker-qdirstat.md @@ -21,17 +21,17 @@ title: qdirstat ## 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/qdirstat` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/qdirstat: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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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: qdirstat: - image: lscr.io/linuxserver/qdirstat + image: lscr.io/linuxserver/qdirstat:latest container_name: qdirstat 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/qdirstat + lscr.io/linuxserver/qdirstat:latest ``` ## Parameters @@ -158,9 +158,10 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to * Container version number * `docker inspect -f '{{ index .Config.Labels "build_version" }}' qdirstat` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/qdirstat` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/qdirstat:latest` ## Versions +* **06.04.22:** - Add xfce terminal. * **13.01.22:** - Compile from source. * **11.01.22:** - Initial release. diff --git a/images/docker-quassel-core.md b/images/docker-quassel-core.md index f0e52875d..d008336f4 100644 --- a/images/docker-quassel-core.md +++ b/images/docker-quassel-core.md @@ -23,17 +23,17 @@ This container handles the IRC connection (quasselcore) and requires a desktop c ## 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/quassel-core` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/quassel-core: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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## Application Setup @@ -105,7 +105,7 @@ To help you get started creating a container from this image you can either use version: "2.1" services: quassel-core: - image: lscr.io/linuxserver/quassel-core + image: lscr.io/linuxserver/quassel-core:latest container_name: quassel-core environment: - PUID=1000 @@ -133,7 +133,7 @@ docker run -d \ -p 113:10113 `#optional` \ -v :/config \ --restart unless-stopped \ - lscr.io/linuxserver/quassel-core + lscr.io/linuxserver/quassel-core:latest ``` ## Parameters @@ -212,7 +212,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to * Container version number * `docker inspect -f '{{ index .Config.Labels "build_version" }}' quassel-core` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/quassel-core` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/quassel-core:latest` ## Versions diff --git a/images/docker-quassel-web.md b/images/docker-quassel-web.md index 083eecbe9..be799f79b 100644 --- a/images/docker-quassel-web.md +++ b/images/docker-quassel-web.md @@ -21,17 +21,17 @@ title: quassel-web ## 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/quassel-web` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/quassel-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 | arm32v6-latest | +| Architecture | Available | Tag | +| :----: | :----: | ---- | +| x86-64 | ✅ | amd64-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## Application Setup @@ -41,6 +41,11 @@ The configuration file using this method can be found at: /config/settings-user.js ``` +### 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. @@ -52,7 +57,7 @@ To help you get started creating a container from this image you can either use version: "2.1" services: quassel-web: - image: lscr.io/linuxserver/quassel-web + image: lscr.io/linuxserver/quassel-web:latest container_name: quassel-web environment: - PUID=1000 @@ -80,7 +85,7 @@ docker run -d \ -p 64443:64443 \ -v /path/to/data:/config \ --restart unless-stopped \ - lscr.io/linuxserver/quassel-web + lscr.io/linuxserver/quassel-web:latest ``` ## Parameters @@ -159,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" }}' quassel-web` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/quassel-web` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/quassel-web:latest` ## Versions diff --git a/images/docker-radarr.md b/images/docker-radarr.md index 7d8a36e9e..7de87c77a 100644 --- a/images/docker-radarr.md +++ b/images/docker-radarr.md @@ -21,27 +21,27 @@ title: radarr ## 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/radarr` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/radarr: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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 Radarr releases | -| develop | Radarr releases from their develop branch | -| nightly | Radarr releases from their nightly branch | +| Tag | Available | Description | +| :----: | :----: |--- | +| latest | ✅ | Stable Radarr releases | +| develop | ✅ | Radarr releases from their develop branch | +| nightly | ✅ | Radarr releases from their nightly branch | ## Application Setup @@ -66,7 +66,7 @@ To help you get started creating a container from this image you can either use version: "2.1" services: radarr: - image: lscr.io/linuxserver/radarr + image: lscr.io/linuxserver/radarr:latest container_name: radarr environment: - PUID=1000 @@ -94,7 +94,7 @@ docker run -d \ -v /path/to/movies:/movies `#optional` \ -v /path/to/downloadclient-downloads:/downloads `#optional` \ --restart unless-stopped \ - lscr.io/linuxserver/radarr + lscr.io/linuxserver/radarr: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" }}' radarr` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/radarr` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/radarr:latest` ## Versions diff --git a/images/docker-raneto.md b/images/docker-raneto.md index f19666546..7196551b9 100644 --- a/images/docker-raneto.md +++ b/images/docker-raneto.md @@ -21,17 +21,17 @@ title: raneto ## 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/raneto` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/raneto: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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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: raneto: - image: lscr.io/linuxserver/raneto + image: lscr.io/linuxserver/raneto:latest container_name: raneto environment: - PUID=1000 @@ -81,7 +81,7 @@ docker run -d \ -p 3000:3000 \ -v /path/to/appdata:/config \ --restart unless-stopped \ - lscr.io/linuxserver/raneto + lscr.io/linuxserver/raneto: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" }}' raneto` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/raneto` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/raneto:latest` ## Versions diff --git a/images/docker-rdesktop.md b/images/docker-rdesktop.md index c2e888faa..3a7dfa42a 100644 --- a/images/docker-rdesktop.md +++ b/images/docker-rdesktop.md @@ -21,48 +21,48 @@ title: rdesktop ## 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/rdesktop` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/rdesktop: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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 | XFCE Alpine | -| ubuntu-xfce | XFCE Ubuntu | -| fedora-xfce | XFCE Fedora | -| arch-xfce | XFCE Arch | -| alpine-kde | KDE Alpine | -| ubuntu-kde | KDE Ubuntu | -| fedora-kde | KDE Fedora | -| arch-kde | KDE Arch | -| alpine-mate | MATE Alpine | -| ubuntu-mate | MATE Ubuntu | -| fedora-mate | MATE Fedora | -| arch-mate | MATE Arch | -| alpine-i3 | i3 Alpine | -| ubuntu-i3 | i3 Ubuntu | -| fedora-i3 | i3 Fedora | -| arch-i3 | i3 Arch | -| alpine-openbox | Openbox Alpine | -| ubuntu-openbox | Openbox Ubuntu | -| fedora-openbox | Openbox Fedora | -| arch-openbox | Openbox Arch | -| alpine-icewm | IceWM Alpine | -| ubuntu-icewm | IceWM Ubuntu | -| fedora-icewm | IceWM Fedora | -| arch-icewm | IceWM Arch | +| Tag | Available | Description | +| :----: | :----: |--- | +| latest | ✅ | XFCE Alpine | +| ubuntu-xfce | ✅ | XFCE Ubuntu | +| fedora-xfce | ✅ | XFCE Fedora | +| arch-xfce | ✅ | XFCE Arch | +| alpine-kde | ✅ | KDE Alpine | +| ubuntu-kde | ✅ | KDE Ubuntu | +| fedora-kde | ✅ | KDE Fedora | +| arch-kde | ✅ | KDE Arch | +| alpine-mate | ✅ | MATE Alpine | +| ubuntu-mate | ✅ | MATE Ubuntu | +| fedora-mate | ✅ | MATE Fedora | +| arch-mate | ✅ | MATE Arch | +| alpine-i3 | ✅ | i3 Alpine | +| ubuntu-i3 | ✅ | i3 Ubuntu | +| fedora-i3 | ✅ | i3 Fedora | +| arch-i3 | ✅ | i3 Arch | +| alpine-openbox | ✅ | Openbox Alpine | +| ubuntu-openbox | ✅ | Openbox Ubuntu | +| fedora-openbox | ✅ | Openbox Fedora | +| arch-openbox | ✅ | Openbox Arch | +| alpine-icewm | ✅ | IceWM Alpine | +| ubuntu-icewm | ✅ | IceWM Ubuntu | +| fedora-icewm | ✅ | IceWM Fedora | +| arch-icewm | ✅ | IceWM Arch | ## Application Setup @@ -115,7 +115,7 @@ To help you get started creating a container from this image you can either use version: "2.1" services: rdesktop: - image: lscr.io/linuxserver/rdesktop + image: lscr.io/linuxserver/rdesktop:latest container_name: rdesktop security_opt: - seccomp:unconfined #optional @@ -149,7 +149,7 @@ docker run -d \ --device /dev/dri:/dev/dri `#optional` \ --shm-size="1gb" `#optional` \ --restart unless-stopped \ - lscr.io/linuxserver/rdesktop + lscr.io/linuxserver/rdesktop:latest ``` ## Parameters @@ -235,7 +235,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to * Container version number * `docker inspect -f '{{ index .Config.Labels "build_version" }}' rdesktop` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/rdesktop` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/rdesktop:latest` ## Versions diff --git a/images/docker-remmina.md b/images/docker-remmina.md index 67d051293..667fa9df8 100644 --- a/images/docker-remmina.md +++ b/images/docker-remmina.md @@ -21,17 +21,17 @@ title: remmina ## 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/remmina` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/remmina: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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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: remmina: - image: lscr.io/linuxserver/remmina + image: lscr.io/linuxserver/remmina:latest container_name: remmina environment: - PUID=1000 @@ -78,7 +78,7 @@ docker run -d \ -p 3000:3000 \ -v /path/to/config:/config \ --restart unless-stopped \ - lscr.io/linuxserver/remmina + lscr.io/linuxserver/remmina: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" }}' remmina` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/remmina` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/remmina:latest` ## Versions diff --git a/images/docker-requestrr.md b/images/docker-requestrr.md index ff208d45b..3445e4c34 100755 --- a/images/docker-requestrr.md +++ b/images/docker-requestrr.md @@ -26,17 +26,17 @@ The upstream dev has ended development. ## 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/requestrr` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/requestrr: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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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: requestrr: - image: lscr.io/linuxserver/requestrr + image: lscr.io/linuxserver/requestrr:latest container_name: requestrr environment: - PUID=1000 @@ -77,7 +77,7 @@ docker run -d \ -p 4545:4545 \ -v /path/to/appdata/config:/config \ --restart unless-stopped \ - lscr.io/linuxserver/requestrr + lscr.io/linuxserver/requestrr: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" }}' requestrr` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/requestrr` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/requestrr:latest` ## Versions diff --git a/images/docker-resilio-sync.md b/images/docker-resilio-sync.md index e7e3c7251..ee688f330 100644 --- a/images/docker-resilio-sync.md +++ b/images/docker-resilio-sync.md @@ -21,17 +21,17 @@ title: resilio-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/resilio-sync` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/resilio-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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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: resilio-sync: - image: lscr.io/linuxserver/resilio-sync + image: lscr.io/linuxserver/resilio-sync:latest container_name: resilio-sync environment: - PUID=1000 @@ -79,7 +79,7 @@ docker run -d \ -v /path/to/downloads:/downloads \ -v /path/to/data:/sync \ --restart unless-stopped \ - lscr.io/linuxserver/resilio-sync + lscr.io/linuxserver/resilio-sync: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" }}' resilio-sync` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/resilio-sync` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/resilio-sync:latest` ## Versions diff --git a/images/docker-rsnapshot.md b/images/docker-rsnapshot.md index d047c28a5..cceaac953 100755 --- a/images/docker-rsnapshot.md +++ b/images/docker-rsnapshot.md @@ -21,17 +21,17 @@ title: rsnapshot ## 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/rsnapshot` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/rsnapshot: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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## Application Setup @@ -69,7 +69,7 @@ To help you get started creating a container from this image you can either use version: "2.1" services: rsnapshot: - image: lscr.io/linuxserver/rsnapshot + image: lscr.io/linuxserver/rsnapshot:latest container_name: rsnapshot environment: - PUID=1000 @@ -94,7 +94,7 @@ docker run -d \ -v :/.snapshots `#optional` \ -v :/data `#optional` \ --restart unless-stopped \ - lscr.io/linuxserver/rsnapshot + lscr.io/linuxserver/rsnapshot: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" }}' rsnapshot` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/rsnapshot` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/rsnapshot:latest` ## Versions diff --git a/images/docker-sabnzbd.md b/images/docker-sabnzbd.md index f797fc4ce..9ee093ce4 100755 --- a/images/docker-sabnzbd.md +++ b/images/docker-sabnzbd.md @@ -21,26 +21,26 @@ title: sabnzbd ## 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/sabnzbd` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/sabnzbd: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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 SABnzbd releases | -| unstable | Pre-releases from their GitHub | +| Tag | Available | Description | +| :----: | :----: |--- | +| latest | ✅ | Stable SABnzbd releases | +| unstable | ✅ | Pre-releases from their GitHub | ## Application Setup @@ -73,7 +73,7 @@ To help you get started creating a container from this image you can either use version: "2.1" services: sabnzbd: - image: lscr.io/linuxserver/sabnzbd + image: lscr.io/linuxserver/sabnzbd:latest container_name: sabnzbd environment: - PUID=1000 @@ -101,7 +101,7 @@ docker run -d \ -v /path/to/downloads:/downloads `#optional` \ -v /path/to/incomplete/downloads:/incomplete-downloads `#optional` \ --restart unless-stopped \ - lscr.io/linuxserver/sabnzbd + lscr.io/linuxserver/sabnzbd: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" }}' sabnzbd` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/sabnzbd` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/sabnzbd:latest` ## Versions diff --git a/images/docker-scrutiny.md b/images/docker-scrutiny.md index 7f8514e1f..b6388011c 100755 --- a/images/docker-scrutiny.md +++ b/images/docker-scrutiny.md @@ -21,17 +21,17 @@ title: scrutiny ## 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/scrutiny` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/scrutiny: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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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: scrutiny: - image: lscr.io/linuxserver/scrutiny + image: lscr.io/linuxserver/scrutiny:latest container_name: scrutiny cap_add: - SYS_RAWIO @@ -100,7 +100,7 @@ docker run -d \ --device /dev/sdb:/dev/sdb \ --device /dev/nvme1n1:/dev/nvme1n1 \ --restart unless-stopped \ - lscr.io/linuxserver/scrutiny + lscr.io/linuxserver/scrutiny:latest ``` ## Parameters @@ -144,6 +144,12 @@ Docker images are configured using parameters passed at runtime (such as those a | Parameter | Function | | :-----: | --- | +### Portainer notice + +{% hint style="warning" %} +This image utilises `cap_add` or `sysctl` to work properly. This is not implemented properly in some versions of Portainer, thus this image may not work if deployed through Portainer. +{% endhint %} + ## Environment variables from files (Docker secrets) You can set any environment variable from a file by using a special prepend `FILE__`. @@ -189,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" }}' scrutiny` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/scrutiny` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/scrutiny:latest` ## Versions diff --git a/images/docker-sickchill.md b/images/docker-sickchill.md index da59e04c5..bef8d553a 100644 --- a/images/docker-sickchill.md +++ b/images/docker-sickchill.md @@ -21,17 +21,17 @@ title: sickchill ## 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/sickchill` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/sickchill: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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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: sickchill: - image: lscr.io/linuxserver/sickchill + image: lscr.io/linuxserver/sickchill:latest container_name: sickchill environment: - PUID=1000 @@ -76,7 +76,7 @@ docker run -d \ -v /path/to/data:/downloads \ -v /path/to/data:/tv \ --restart unless-stopped \ - lscr.io/linuxserver/sickchill + lscr.io/linuxserver/sickchill: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" }}' sickchill` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/sickchill` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/sickchill:latest` ## Versions diff --git a/images/docker-sickgear.md b/images/docker-sickgear.md index 68b31a73e..653bce6b9 100644 --- a/images/docker-sickgear.md +++ b/images/docker-sickgear.md @@ -23,17 +23,17 @@ For more information on SickGear visit their website and check it out: https://g ## 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/sickgear` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/sickgear: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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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: sickgear: - image: lscr.io/linuxserver/sickgear + image: lscr.io/linuxserver/sickgear:latest container_name: sickgear environment: - PUID=1000 @@ -104,7 +104,7 @@ docker run -d \ -v /path/to/data:/tv \ -v /path/to/data:/downloads \ --restart unless-stopped \ - lscr.io/linuxserver/sickgear + lscr.io/linuxserver/sickgear: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" }}' sickgear` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/sickgear` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/sickgear:latest` ## Versions diff --git a/images/docker-smokeping.md b/images/docker-smokeping.md index 8c174ea7c..1044f7c7d 100644 --- a/images/docker-smokeping.md +++ b/images/docker-smokeping.md @@ -21,17 +21,17 @@ title: smokeping ## 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/smokeping` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/smokeping: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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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: smokeping: - image: lscr.io/linuxserver/smokeping + image: lscr.io/linuxserver/smokeping:latest container_name: smokeping environment: - PUID=1000 @@ -76,7 +76,7 @@ docker run -d \ -v :/config \ -v :/data \ --restart unless-stopped \ - lscr.io/linuxserver/smokeping + lscr.io/linuxserver/smokeping: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" }}' smokeping` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/smokeping` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/smokeping:latest` ## Versions diff --git a/images/docker-snapdrop.md b/images/docker-snapdrop.md index 305abcba4..05eb18aa3 100755 --- a/images/docker-snapdrop.md +++ b/images/docker-snapdrop.md @@ -21,17 +21,17 @@ title: snapdrop ## 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/snapdrop` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/snapdrop: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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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: snapdrop: - image: lscr.io/linuxserver/snapdrop + image: lscr.io/linuxserver/snapdrop:latest container_name: snapdrop environment: - PUID=1000 @@ -76,7 +76,7 @@ docker run -d \ -p 443:443 \ -v :/config \ --restart unless-stopped \ - lscr.io/linuxserver/snapdrop + lscr.io/linuxserver/snapdrop: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" }}' snapdrop` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/snapdrop` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/snapdrop:latest` ## Versions diff --git a/images/docker-snipe-it.md b/images/docker-snipe-it.md index c62310c14..bd9e39838 100644 --- a/images/docker-snipe-it.md +++ b/images/docker-snipe-it.md @@ -21,17 +21,17 @@ title: snipe-it ## 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/snipe-it` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/snipe-it: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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## Application Setup @@ -84,7 +84,7 @@ To help you get started creating a container from this image you can either use version: "2.1" services: snipe-it: - image: lscr.io/linuxserver/snipe-it + image: lscr.io/linuxserver/snipe-it:latest container_name: snipe-it environment: - PUID=1000 @@ -120,7 +120,7 @@ docker run -d \ -p 8080:80 \ -v :/config \ --restart unless-stopped \ - lscr.io/linuxserver/snipe-it + lscr.io/linuxserver/snipe-it:latest ``` ## Parameters @@ -203,10 +203,12 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to * Container version number * `docker inspect -f '{{ index .Config.Labels "build_version" }}' snipe-it` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/snipe-it` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/snipe-it:latest` ## Versions +* **14.05.22:** - Add php7-sodium for v6. +* **12.04.22:** - Don't build development elements. * **02.03.22:** - Rework init logic, do not show default compose. * **29.06.21:** - Rebasing to alpine 3.14. * **30.04.21:** - Rebasing to alpine 3.13, add artisan migrate on spinup. diff --git a/images/docker-sonarr.md b/images/docker-sonarr.md index 7e55dac37..975e2d544 100644 --- a/images/docker-sonarr.md +++ b/images/docker-sonarr.md @@ -21,26 +21,26 @@ title: sonarr ## 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/sonarr` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/sonarr: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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 Sonarr (currently v3) | -| develop | Development releases from Sonarr (currently v3) | +| Tag | Available | Description | +| :----: | :----: |--- | +| latest | ✅ | Stable releases from Sonarr (currently v3) | +| develop | ✅ | Development releases from Sonarr (currently v3) | ## 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: sonarr: - image: lscr.io/linuxserver/sonarr + image: lscr.io/linuxserver/sonarr:latest container_name: sonarr environment: - PUID=1000 @@ -93,7 +93,7 @@ docker run -d \ -v /path/to/tvseries:/tv `#optional` \ -v /path/to/downloadclient-downloads:/downloads `#optional` \ --restart unless-stopped \ - lscr.io/linuxserver/sonarr + lscr.io/linuxserver/sonarr:latest ``` ## Parameters @@ -172,10 +172,11 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to * Container version number * `docker inspect -f '{{ index .Config.Labels "build_version" }}' sonarr` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/sonarr` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/sonarr:latest` ## Versions +* **28.04.22:** - Rebase master branch to mono 6.12 base (focal). * **20.02.22:** - Rebase develop branch to Alpine, deprecate develop-alpine branch. * **28.12.21:** - Add develop-alpine branch. * **11.05.21:** - Make the paths clearer to the user. diff --git a/images/docker-sqlitebrowser.md b/images/docker-sqlitebrowser.md index 1618d85da..0e1a1c614 100755 --- a/images/docker-sqlitebrowser.md +++ b/images/docker-sqlitebrowser.md @@ -21,17 +21,17 @@ title: sqlitebrowser ## 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/sqlitebrowser` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/sqlitebrowser: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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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: sqlitebrowser: - image: lscr.io/linuxserver/sqlitebrowser + image: lscr.io/linuxserver/sqlitebrowser:latest container_name: sqlitebrowser environment: - PUID=1000 @@ -74,7 +74,7 @@ docker run -d \ -p 3000:3000 \ -v /path/to/config:/config \ --restart unless-stopped \ - lscr.io/linuxserver/sqlitebrowser + lscr.io/linuxserver/sqlitebrowser: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" }}' sqlitebrowser` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/sqlitebrowser` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/sqlitebrowser:latest` ## Versions diff --git a/images/docker-swag.md b/images/docker-swag.md index 1a245840c..d918b0e07 100755 --- a/images/docker-swag.md +++ b/images/docker-swag.md @@ -21,17 +21,17 @@ SWAG - Secure Web Application Gateway (formerly known as letsencrypt, no relatio ## 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/swag` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/swag: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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## Application Setup @@ -78,11 +78,12 @@ This will *ask* Google et al not to index and list your site. Be careful with th ### Using fail2ban -* This container includes fail2ban set up with 4 jails by default: +* This container includes fail2ban set up with 5 jails by default: 1. nginx-http-auth 2. nginx-badbots 3. nginx-botsearch 4. nginx-deny + 5. nginx-unauthorized * To enable or disable other jails, modify the file `/config/fail2ban/jail.local` * To modify filters and actions, instead of editing the `.conf` files, create `.local` files with the same name and edit those because .conf files get overwritten when the actions and filters are updated. `.local` files will append whatever's in the `.conf` files (ie. `nginx-http-auth.conf` --> `nginx-http-auth.local`) * You can check which jails are active via `docker exec -it swag fail2ban-client status` @@ -118,7 +119,7 @@ To help you get started creating a container from this image you can either use version: "2.1" services: swag: - image: lscr.io/linuxserver/swag + image: lscr.io/linuxserver/swag:latest container_name: swag cap_add: - NET_ADMIN @@ -169,7 +170,7 @@ docker run -d \ -p 80:80 `#optional` \ -v /path/to/appdata/config:/config \ --restart unless-stopped \ - lscr.io/linuxserver/swag + lscr.io/linuxserver/swag:latest ``` ## Parameters @@ -194,7 +195,7 @@ Docker images are configured using parameters passed at runtime (such as those a | `VALIDATION=http` | Certbot validation method to use, options are `http`, `dns` or `duckdns` (`dns` method also requires `DNSPLUGIN` variable set) (`duckdns` method requires `DUCKDNSTOKEN` variable set, and the `SUBDOMAINS` variable must be either empty or set to `wildcard`). | | `SUBDOMAINS=www,` | Subdomains you'd like the cert to cover (comma separated, no spaces) ie. `www,ftp,cloud`. For a wildcard cert, set this _exactly_ to `wildcard` (wildcard cert is available via `dns` and `duckdns` validation only) | | `CERTPROVIDER=` | Optionally define the cert provider. Set to `zerossl` for ZeroSSL certs (requires existing [ZeroSSL account](https://app.zerossl.com/signup) and the e-mail address entered in `EMAIL` env var). Otherwise defaults to Let's Encrypt. | -| `DNSPLUGIN=cloudflare` | Required if `VALIDATION` is set to `dns`. Options are `aliyun`, `cloudflare`, `cloudxns`, `cpanel`, `desec`, `digitalocean`, `directadmin`, `dnsimple`, `dnsmadeeasy`, `dnspod`, `domeneshop`, `gandi`, `gehirn`, `google`, `he`, `hetzner`, `infomaniak`, `inwx`, `ionos`, `linode`, `luadns`, `netcup`, `njalla`, `nsone`, `ovh`, `rfc2136`, `route53`, `sakuracloud`, `transip` and `vultr`. Also need to enter the credentials into the corresponding ini (or json for some plugins) file under `/config/dns-conf`. | +| `DNSPLUGIN=cloudflare` | Required if `VALIDATION` is set to `dns`. Options are `aliyun`, `azure`, `cloudflare`, `cloudxns`, `cpanel`, `desec`, `digitalocean`, `directadmin`, `dnsimple`, `dnsmadeeasy`, `dnspod`, `domeneshop`, `gandi`, `gehirn`, `google`, `he`, `hetzner`, `infomaniak`, `inwx`, `ionos`, `linode`, `loopia`, `luadns`, `netcup`, `njalla`, `nsone`, `ovh`, `rfc2136`, `route53`, `sakuracloud`, `standalone`, `transip` and `vultr`. Also need to enter the credentials into the corresponding ini (or json for some plugins) file under `/config/dns-conf`. | | `PROPAGATION=` | Optionally override (in seconds) the default propagation time for the dns plugins. | | `DUCKDNSTOKEN=` | Required if `VALIDATION` is set to `duckdns`. Retrieve your token from https://www.duckdns.org | | `EMAIL=` | Optional e-mail address used for cert expiration notifications (Required for ZeroSSL). | @@ -213,6 +214,12 @@ Docker images are configured using parameters passed at runtime (such as those a | Parameter | Function | | :-----: | --- | +### Portainer notice + +{% hint style="warning" %} +This image utilises `cap_add` or `sysctl` to work properly. This is not implemented properly in some versions of Portainer, thus this image may not work if deployed through Portainer. +{% endhint %} + ## Environment variables from files (Docker secrets) You can set any environment variable from a file by using a special prepend `FILE__`. @@ -258,10 +265,13 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to * Container version number * `docker inspect -f '{{ index .Config.Labels "build_version" }}' swag` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/swag` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/swag:latest` ## Versions +* **18.05.22:** - Added support for Azure DNS validation. +* **09.04.22:** - Added certbot-dns-loopia for DNS01 validation. +* **05.04.22:** - Added support for standalone DNS validation. * **28.03.22:** - created a logfile for fail2ban nginx-unauthorized in /etc/cont-init.d/50-config * **09.01.22:** - Added a fail2ban jail for nginx unauthorized * **21.12.21:** - Fixed issue with iptables not working as expected diff --git a/images/docker-synclounge.md b/images/docker-synclounge.md index a866fa3b8..bd69d8581 100644 --- a/images/docker-synclounge.md +++ b/images/docker-synclounge.md @@ -21,17 +21,17 @@ title: synclounge ## 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/synclounge` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/synclounge: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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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: synclounge: - image: lscr.io/linuxserver/synclounge + image: lscr.io/linuxserver/synclounge:latest container_name: synclounge environment: - TZ=Europe/London @@ -73,7 +73,7 @@ docker run -d \ -e AUTOJOIN_ROOM=roomname `#optional` \ -p 8088:8088 \ --restart unless-stopped \ - lscr.io/linuxserver/synclounge + lscr.io/linuxserver/synclounge:latest ``` ## Parameters @@ -137,7 +137,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to * Container version number * `docker inspect -f '{{ index .Config.Labels "build_version" }}' synclounge` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/synclounge` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/synclounge:latest` ## Versions diff --git a/images/docker-syncthing.md b/images/docker-syncthing.md index 17f289b34..d50a3a60b 100644 --- a/images/docker-syncthing.md +++ b/images/docker-syncthing.md @@ -21,17 +21,17 @@ title: syncthing ## 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/syncthing` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/syncthing: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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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: syncthing: - image: lscr.io/linuxserver/syncthing + image: lscr.io/linuxserver/syncthing:latest container_name: syncthing hostname: syncthing #optional environment: @@ -84,7 +84,7 @@ docker run -d \ -v /path/to/data1:/data1 \ -v /path/to/data2:/data2 \ --restart unless-stopped \ - lscr.io/linuxserver/syncthing + lscr.io/linuxserver/syncthing: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" }}' syncthing` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/syncthing` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/syncthing:latest` ## Versions +* **03.05.21:** - Rebase to alpine 3.15 (builds on edge for go 1.18). * **05.10.21:** - Rebase to alpine 3.14. * **12.05.21:** - Remove sysctl parameter again * **03.05.21:** - Raise maximum UDP buffer size. diff --git a/images/docker-syslog-ng.md b/images/docker-syslog-ng.md index 0cffc1c53..1eceb9646 100755 --- a/images/docker-syslog-ng.md +++ b/images/docker-syslog-ng.md @@ -21,17 +21,17 @@ title: syslog-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/syslog-ng` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/syslog-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 | latest | -| arm64 | arm64v8-latest | -| armhf | arm32v7-latest | +| Architecture | Available | Tag | +| :----: | :----: | ---- | +| x86-64 | ✅ | amd64-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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: syslog-ng: - image: lscr.io/linuxserver/syslog-ng + image: lscr.io/linuxserver/syslog-ng:latest container_name: syslog-ng environment: - PUID=1000 @@ -80,7 +80,7 @@ docker run -d \ -v /path/to/config:/config \ -v /path/to/log:/var/log `#optional` \ --restart unless-stopped \ - lscr.io/linuxserver/syslog-ng + lscr.io/linuxserver/syslog-ng: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" }}' syslog-ng` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/syslog-ng` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/syslog-ng:latest` ## Versions diff --git a/images/docker-tautulli.md b/images/docker-tautulli.md index fa22290d6..94d4da680 100644 --- a/images/docker-tautulli.md +++ b/images/docker-tautulli.md @@ -21,26 +21,26 @@ title: tautulli ## 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/tautulli` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/tautulli: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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 Tautulli releases | -| develop | Built at head of Tautulli nightly branch | +| Tag | Available | Description | +| :----: | :----: |--- | +| latest | ✅ | Stable Tautulli releases | +| develop | ✅ | Built at head of Tautulli nightly 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: tautulli: - image: lscr.io/linuxserver/tautulli + image: lscr.io/linuxserver/tautulli:latest container_name: tautulli environment: - PUID=1000 @@ -82,7 +82,7 @@ docker run -d \ -p 8181:8181 \ -v :/config \ --restart unless-stopped \ - lscr.io/linuxserver/tautulli + lscr.io/linuxserver/tautulli: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" }}' tautulli` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/tautulli` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/tautulli:latest` ## Versions diff --git a/images/docker-tester.md b/images/docker-tester.md index 2e80d1224..7bc6ce4ba 100755 --- a/images/docker-tester.md +++ b/images/docker-tester.md @@ -23,13 +23,16 @@ This internal tool is used as a desktop sandbox in our CI process to grab a scre 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/tester` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/tester: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-\ | +| arm64 | ❌ | | +| armhf| ❌ | | + ## Usage @@ -42,7 +45,7 @@ To help you get started creating a container from this image you can either use version: "2.1" services: tester: - image: lscr.io/linuxserver/tester + image: lscr.io/linuxserver/tester:latest container_name: tester environment: - URL=http://google.com @@ -59,7 +62,7 @@ docker run -d \ -e URL=http://google.com \ -p 3000:3000 \ --restart unless-stopped \ - lscr.io/linuxserver/tester + lscr.io/linuxserver/tester:latest ``` ## Parameters @@ -120,7 +123,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to * Container version number * `docker inspect -f '{{ index .Config.Labels "build_version" }}' tester` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/tester` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/tester:latest` ## Versions diff --git a/images/docker-thelounge.md b/images/docker-thelounge.md index 042b065d2..1ae49ede2 100644 --- a/images/docker-thelounge.md +++ b/images/docker-thelounge.md @@ -21,33 +21,55 @@ title: thelounge ## 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/thelounge` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/thelounge: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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | + +## Version Tags + +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 | Available | Description | +| :----: | :----: |--- | +| latest | ✅ | Stable releases. | +| next | ✅ | Next Pre-Releases. | +| nightly | ✅ | Nightly images from commits in master. | ## Application Setup * When the application first runs, it will populate its /config + * Stop the container + * Now from the host, edit `/config/config.js`, wherever you've mapped it + * In most cases you want the value `public: false` to allow named users only + * Setting the two prefetch values to true improves usability, but uses more storage + * Once you have the configuration you want, save it and start the container again + * For each user, run the command + * `docker exec -it thelounge s6-setuidgid abc thelounge add ` + * You will be prompted to enter a password that will not be echoed. + * Saving logs to disk is the default, this consumes more space but allows scrollback. + * To log in to the application, browse to `http://:9000` + * You should now be prompted for a username and password on the webinterface. -* Once logged in, you can add an IRC network. Some defaults are preset for Freenode. + +* Once logged in, you can add an IRC network. Some defaults are preset for Freenode ## Usage @@ -60,7 +82,7 @@ To help you get started creating a container from this image you can either use version: "2.1" services: thelounge: - image: lscr.io/linuxserver/thelounge + image: lscr.io/linuxserver/thelounge:latest container_name: thelounge environment: - PUID=1000 @@ -84,7 +106,7 @@ docker run -d \ -p 9000:9000 \ -v :/config \ --restart unless-stopped \ - lscr.io/linuxserver/thelounge + lscr.io/linuxserver/thelounge:latest ``` ## Parameters @@ -161,10 +183,12 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to * Container version number * `docker inspect -f '{{ index .Config.Labels "build_version" }}' thelounge` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/thelounge` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/thelounge:latest` ## Versions +* **12.04.22:** - Install from source using yarn. +* **11.04.22:** - Rebasing to alpine 3.15 and switching from python2-dev to python3-dev for building node sqlite on arm. * **23.01.21:** - Rebasing to alpine 3.13. * **02.06.20:** - Rebasing to alpine 3.12. * **19.12.19:** - Rebasing to alpine 3.11. diff --git a/images/docker-transmission.md b/images/docker-transmission.md index a0ff799bd..fda3c2779 100644 --- a/images/docker-transmission.md +++ b/images/docker-transmission.md @@ -21,17 +21,17 @@ title: transmission ## 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/transmission` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/transmission: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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## Application Setup @@ -72,7 +72,7 @@ To help you get started creating a container from this image you can either use version: "2.1" services: transmission: - image: lscr.io/linuxserver/transmission + image: lscr.io/linuxserver/transmission:latest container_name: transmission environment: - PUID=1000 @@ -83,11 +83,11 @@ services: - PASS=password #optional - WHITELIST=iplist #optional - PEERPORT=peerport #optional - - HOST_WHITELIST=dnsnane list #optional + - HOST_WHITELIST=dnsname list #optional volumes: - - :/config - - :/downloads - - :/watch + - /path/to/data:/config + - /path/to/downloads:/downloads + - /path/to/watch/folder:/watch ports: - 9091:9091 - 51413:51413 @@ -108,15 +108,15 @@ docker run -d \ -e PASS=password `#optional` \ -e WHITELIST=iplist `#optional` \ -e PEERPORT=peerport `#optional` \ - -e HOST_WHITELIST=dnsnane list `#optional` \ + -e HOST_WHITELIST=dnsname list `#optional` \ -p 9091:9091 \ -p 51413:51413 \ -p 51413:51413/udp \ - -v :/config \ - -v :/downloads \ - -v :/watch \ + -v /path/to/data:/config \ + -v /path/to/downloads:/downloads \ + -v /path/to/watch/folder:/watch \ --restart unless-stopped \ - lscr.io/linuxserver/transmission + lscr.io/linuxserver/transmission:latest ``` ## Parameters @@ -138,12 +138,12 @@ 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. | -| `TRANSMISSION_WEB_HOME=/combustion-release/` | Specify an alternative UI options are [`/combustion-release/`](https://github.com/Secretmapper/combustion), [`/transmission-web-control/`](https://github.com/ronggang/transmission-web-control), [`/kettu/`](https://github.com/endor/kettu) and [`/flood-for-transmission/`](https://github.com/johman10/flood-for-transmission). | +| `TRANSMISSION_WEB_HOME=/combustion-release/` | Specify an alternative UI options are [`/combustion-release/`](https://github.com/Secretmapper/combustion), [`/transmission-web-control/`](https://github.com/ronggang/transmission-web-control), [`/kettu/`](https://github.com/endor/kettu), [`/flood-for-transmission/`](https://github.com/johman10/flood-for-transmission), and [`/transmissionic/`](https://github.com/6c65726f79/Transmissionic). | | `USER=username` | Specify an optional username for the interface | | `PASS=password` | Specify an optional password for the interface | -| `WHITELIST=iplist` | Specify an optional list of comma separated ip whitelist. Fill rpc-whitelist setting. | -| `PEERPORT=peerport` | Specify an optional port for torrent TCP/UDP connections. Fill peer-port setting. | -| `HOST_WHITELIST=dnsnane list` | Specify an optional list of comma separated dns name whitelist. Fill rpc-host-whitelist setting. | +| `WHITELIST=iplist` | Specify an optional list of comma separated ip whitelist. Fills rpc-whitelist setting. | +| `PEERPORT=peerport` | Specify an optional port for torrent TCP/UDP connections. Fills peer-port setting. | +| `HOST_WHITELIST=dnsname list` | Specify an optional list of comma separated dns name whitelist. Fills rpc-host-whitelist setting. | ### Volume Mappings (`-v`) @@ -203,10 +203,11 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to * Container version number * `docker inspect -f '{{ index .Config.Labels "build_version" }}' transmission` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/transmission` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/transmission:latest` ## Versions +* **03.04.22:** - Add Transmissionic as a UI option. * **21.02.22:** - Build unrar from source, rebase to Alpine 3.15, add symlinks neeeded for TWC. Credit @alexbelgium * **09.07.21:** - Wait for the transmission-daemon termination after a caught sigterm. * **06.03.21:** - Add Flood for Transmission as a UI option. @@ -232,7 +233,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to * **25.07.17:** - Add rsync package. * **27.05.17:** - Rebase to alpine linux 3.6. * **06.02.17:** - Rebase to alpine linux 3.5. -* **15.01.17:** - Add p7zip, tar , unrar and unzip packages. +* **15.01.17:** - Add p7zip, tar, unrar, and unzip packages. * **16.10.16:** - Blocklist autoupdate with optional authentication. * **14.10.16:** - Add version layer informationE. * **23.09.16:** - Add information about securing the webui to README. diff --git a/images/docker-tvheadend.md b/images/docker-tvheadend.md index 60bee9f3a..94cb23e78 100644 --- a/images/docker-tvheadend.md +++ b/images/docker-tvheadend.md @@ -23,26 +23,26 @@ Multiple EPG sources are supported (over-the-air DVB and ATSC including OpenTV D ## 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/tvheadend` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/tvheadend: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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 release. | -| release-4.2 | Latest release from 4.2 branch. | +| Tag | Available | Description | +| :----: | :----: |--- | +| latest | ✅ | Current latest release. | +| release-4.2 | ✅ | Latest release from 4.2 branch. | ## Application Setup @@ -115,7 +115,7 @@ To help you get started creating a container from this image you can either use version: "2.1" services: tvheadend: - image: lscr.io/linuxserver/tvheadend + image: lscr.io/linuxserver/tvheadend:latest container_name: tvheadend environment: - PUID=1000 @@ -150,7 +150,7 @@ docker run -d \ --device /dev/dri:/dev/dri `#optional` \ --device /dev/dvb:/dev/dvb `#optional` \ --restart unless-stopped \ - lscr.io/linuxserver/tvheadend + lscr.io/linuxserver/tvheadend:latest ``` #### Host vs. Bridge @@ -242,10 +242,11 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to * Container version number * `docker inspect -f '{{ index .Config.Labels "build_version" }}' tvheadend` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/tvheadend` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/tvheadend:latest` ## Versions +* **16.04.22:** - Added URL XMLTV grabber. * **05.01.22:** - Rebase to Alpine 3.15. Disable execinfo to fix builds. Update xmltv. * **11.05.21:** - Added Intel iHD driver support. * **02.06.20:** - Update to Alpine 3.12. diff --git a/images/docker-ubooquity.md b/images/docker-ubooquity.md index 27d291f8f..14cb12539 100644 --- a/images/docker-ubooquity.md +++ b/images/docker-ubooquity.md @@ -21,17 +21,17 @@ title: ubooquity ## 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/ubooquity` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/ubooquity: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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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: ubooquity: - image: lscr.io/linuxserver/ubooquity + image: lscr.io/linuxserver/ubooquity:latest container_name: ubooquity environment: - PUID=1000 @@ -97,7 +97,7 @@ docker run -d \ -v :/comics \ -v :/files \ --restart unless-stopped \ - lscr.io/linuxserver/ubooquity + lscr.io/linuxserver/ubooquity: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" }}' ubooquity` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/ubooquity` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/ubooquity:latest` ## Versions diff --git a/images/docker-unifi-controller.md b/images/docker-unifi-controller.md index 5387f5b49..89eb9c3c9 100644 --- a/images/docker-unifi-controller.md +++ b/images/docker-unifi-controller.md @@ -21,17 +21,17 @@ The [Unifi-controller](https://www.ubnt.com/enterprise/#unifi) software is a pow ## 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/unifi-controller` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/unifi-controller: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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## Application Setup @@ -50,6 +50,11 @@ The default device password is `ubnt`. `$address` is the IP address of the host When using a Security Gateway (router) it could be that network connected devices are unable to obtain an ip address. This can be fixed by setting "DHCP Gateway IP", under Settings > Networks > network_name, to a correct (and accessable) ip address. +### 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. @@ -61,7 +66,7 @@ To help you get started creating a container from this image you can either use version: "2.1" services: unifi-controller: - image: lscr.io/linuxserver/unifi-controller + image: lscr.io/linuxserver/unifi-controller:latest container_name: unifi-controller environment: - PUID=1000 @@ -103,7 +108,7 @@ docker run -d \ -p 5514:5514/udp `#optional` \ -v :/config \ --restart unless-stopped \ - lscr.io/linuxserver/unifi-controller + lscr.io/linuxserver/unifi-controller:latest ``` ## Parameters @@ -189,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" }}' unifi-controller` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/unifi-controller` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/unifi-controller:latest` ## Versions diff --git a/images/docker-webgrabplus.md b/images/docker-webgrabplus.md index 27dccf631..fbb1920fe 100644 --- a/images/docker-webgrabplus.md +++ b/images/docker-webgrabplus.md @@ -21,17 +21,17 @@ title: webgrabplus ## 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/webgrabplus` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/webgrabplus: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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## Application Setup @@ -76,8 +76,10 @@ To help you get started creating a container from this image you can either use version: "2.1" services: webgrabplus: - image: lscr.io/linuxserver/webgrabplus + image: lscr.io/linuxserver/webgrabplus:latest container_name: webgrabplus + hostname: webgrabplus + mac_address: 00:00:00:00:00:00 environment: - PUID=1000 - PGID=1000 @@ -93,13 +95,15 @@ services: ```bash docker run -d \ --name=webgrabplus \ + --hostname=webgrabplus \ + --mac-address=00:00:00:00:00:00 \ -e PUID=1000 \ -e PGID=1000 \ -e TZ=Europe/London \ -v /path/to/config:/config \ -v /path/to/data:/data \ --restart unless-stopped \ - lscr.io/linuxserver/webgrabplus + lscr.io/linuxserver/webgrabplus:latest ``` ## Parameters @@ -130,6 +134,8 @@ Docker images are configured using parameters passed at runtime (such as those a | Parameter | Function | | :-----: | --- | +| `--hostname=` | Set the hostname for the container for the license check. | +| `--mac-address=` | Set the mac_address for the container for the license check. | ## Environment variables from files (Docker secrets) @@ -176,10 +182,11 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to * Container version number * `docker inspect -f '{{ index .Config.Labels "build_version" }}' webgrabplus` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/webgrabplus` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/webgrabplus:latest` ## Versions +* **29.04.22:** - Add `hostname` and `mac_address` arguments that are needed for the license check to compose and cli samples. * **23.03.22:** - Rebase to Alpine 3.15. * **23.03.22:** - Update to use dotnet instead of mono. * **06.01.22:** - Rebase to Ubuntu focal. Enable auto builds on version updates (beta and stable). diff --git a/images/docker-webtop.md b/images/docker-webtop.md index 7dbe5f9a5..560aa80e1 100755 --- a/images/docker-webtop.md +++ b/images/docker-webtop.md @@ -21,48 +21,48 @@ title: webtop ## 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/webtop` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/webtop: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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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 | XFCE Alpine | -| ubuntu-xfce | XFCE Ubuntu | -| fedora-xfce | XFCE Fedora | -| arch-xfce | XFCE Arch | -| alpine-kde | KDE Alpine | -| ubuntu-kde | KDE Ubuntu | -| fedora-kde | KDE Fedora | -| arch-kde | KDE Arch | -| alpine-mate | MATE Alpine | -| ubuntu-mate | MATE Ubuntu | -| fedora-mate | MATE Fedora | -| arch-mate | MATE Arch | -| alpine-i3 | i3 Alpine | -| ubuntu-i3 | i3 Ubuntu | -| fedora-i3 | i3 Fedora | -| arch-i3 | i3 Arch | -| alpine-openbox | Openbox Alpine | -| ubuntu-openbox | Openbox Ubuntu | -| fedora-openbox | Openbox Fedora | -| arch-openbox | Openbox Arch | -| alpine-icewm | IceWM Alpine | -| ubuntu-icewm | IceWM Ubuntu | -| fedora-icewm | IceWM Fedora | -| arch-icewm | IceWM Arch | +| Tag | Available | Description | +| :----: | :----: |--- | +| latest | ✅ | XFCE Alpine | +| ubuntu-xfce | ✅ | XFCE Ubuntu | +| fedora-xfce | ✅ | XFCE Fedora | +| arch-xfce | ✅ | XFCE Arch | +| alpine-kde | ✅ | KDE Alpine | +| ubuntu-kde | ✅ | KDE Ubuntu | +| fedora-kde | ✅ | KDE Fedora | +| arch-kde | ✅ | KDE Arch | +| alpine-mate | ✅ | MATE Alpine | +| ubuntu-mate | ✅ | MATE Ubuntu | +| fedora-mate | ✅ | MATE Fedora | +| arch-mate | ✅ | MATE Arch | +| alpine-i3 | ✅ | i3 Alpine | +| ubuntu-i3 | ✅ | i3 Ubuntu | +| fedora-i3 | ✅ | i3 Fedora | +| arch-i3 | ✅ | i3 Arch | +| alpine-openbox | ✅ | Openbox Alpine | +| ubuntu-openbox | ✅ | Openbox Ubuntu | +| fedora-openbox | ✅ | Openbox Fedora | +| arch-openbox | ✅ | Openbox Arch | +| alpine-icewm | ✅ | IceWM Alpine | +| ubuntu-icewm | ✅ | IceWM Ubuntu | +| fedora-icewm | ✅ | IceWM Fedora | +| arch-icewm | ✅ | IceWM Arch | ## Application Setup @@ -141,7 +141,7 @@ To help you get started creating a container from this image you can either use version: "2.1" services: webtop: - image: lscr.io/linuxserver/webtop + image: lscr.io/linuxserver/webtop:latest container_name: webtop security_opt: - seccomp:unconfined #optional @@ -179,7 +179,7 @@ docker run -d \ --device /dev/dri:/dev/dri `#optional` \ --shm-size="1gb" `#optional` \ --restart unless-stopped \ - lscr.io/linuxserver/webtop + lscr.io/linuxserver/webtop:latest ``` ## Parameters @@ -267,7 +267,7 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to * Container version number * `docker inspect -f '{{ index .Config.Labels "build_version" }}' webtop` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/webtop` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/webtop:latest` ## Versions diff --git a/images/docker-wikijs.md b/images/docker-wikijs.md index 859a12acd..4420b6c2f 100755 --- a/images/docker-wikijs.md +++ b/images/docker-wikijs.md @@ -21,17 +21,18 @@ title: wikijs ## 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/wikijs` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/wikijs: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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | + ## Usage @@ -44,7 +45,7 @@ To help you get started creating a container from this image you can either use version: "2.1" services: wikijs: - image: lscr.io/linuxserver/wikijs + image: lscr.io/linuxserver/wikijs:latest container_name: wikijs environment: - PUID=1000 @@ -70,7 +71,7 @@ docker run -d \ -v :/config \ -v :/data \ --restart unless-stopped \ - lscr.io/linuxserver/wikijs + lscr.io/linuxserver/wikijs:latest ``` ## Parameters @@ -148,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" }}' wikijs` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/wikijs` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/wikijs:latest` ## Versions diff --git a/images/docker-wireguard.md b/images/docker-wireguard.md index 08068b7b8..663a2ab28 100644 --- a/images/docker-wireguard.md +++ b/images/docker-wireguard.md @@ -20,17 +20,17 @@ title: wireguard ## 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/wireguard` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/wireguard: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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## Application Setup @@ -107,7 +107,7 @@ To help you get started creating a container from this image you can either use version: "2.1" services: wireguard: - image: lscr.io/linuxserver/wireguard + image: lscr.io/linuxserver/wireguard:latest container_name: wireguard cap_add: - NET_ADMIN @@ -122,6 +122,7 @@ services: - PEERDNS=auto #optional - INTERNAL_SUBNET=10.13.13.0 #optional - ALLOWEDIPS=0.0.0.0/0 #optional + - LOG_CONFS=true #optional volumes: - /path/to/appdata/config:/config - /lib/modules:/lib/modules @@ -148,12 +149,13 @@ docker run -d \ -e PEERDNS=auto `#optional` \ -e INTERNAL_SUBNET=10.13.13.0 `#optional` \ -e ALLOWEDIPS=0.0.0.0/0 `#optional` \ + -e LOG_CONFS=true `#optional` \ -p 51820:51820/udp \ -v /path/to/appdata/config:/config \ -v /lib/modules:/lib/modules \ --sysctl="net.ipv4.conf.all.src_valid_mark=1" \ --restart unless-stopped \ - lscr.io/linuxserver/wireguard + lscr.io/linuxserver/wireguard:latest ``` ## Parameters @@ -179,6 +181,7 @@ Docker images are configured using parameters passed at runtime (such as those a | `PEERDNS=auto` | DNS server set in peer/client configs (can be set as `8.8.8.8`). Used in server mode. Defaults to `auto`, which uses wireguard docker host's DNS via included CoreDNS forward. | | `INTERNAL_SUBNET=10.13.13.0` | Internal subnet for the wireguard and server and peers (only change if it clashes). Used in server mode. | | `ALLOWEDIPS=0.0.0.0/0` | The IPs/Ranges that the peers will be able to reach using the VPN connection. If not specified the default value is: '0.0.0.0/0, ::0/0' This will cause ALL traffic to route through the VPN, if you want split tunneling, set this to only the IPs you would like to use the tunnel AND the ip of the server's WG ip, such as 10.13.13.1. | +| `LOG_CONFS=true` | Generated QR codes will be displayed in the docker log. Set to `false` to skip log output. | ### Volume Mappings (`-v`) @@ -193,6 +196,12 @@ Docker images are configured using parameters passed at runtime (such as those a | :-----: | --- | | `--sysctl=` | Required for client mode. | +### Portainer notice + +{% hint style="warning" %} +This image utilises `cap_add` or `sysctl` to work properly. This is not implemented properly in some versions of Portainer, thus this image may not work if deployed through Portainer. +{% endhint %} + ## Environment variables from files (Docker secrets) You can set any environment variable from a file by using a special prepend `FILE__`. @@ -238,10 +247,13 @@ We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to * Container version number * `docker inspect -f '{{ index .Config.Labels "build_version" }}' wireguard` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/wireguard` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/wireguard:latest` ## Versions +* **16.05.22:** - Improve NAT handling in server mode when multiple ethernet devices are present. +* **23.04.22:** - Add pre-shared key support. Automatically added to all new peer confs generated, existing ones are left without to ensure no breaking changes. +* **10.04.22:** - Rebase to Ubuntu Focal. Add `LOG_CONFS` env var. Remove deprecated `add-peer` command. * **28.10.21:** - Add site-to-site vpn support. * **11.02.21:** - Fix bug related to changing internal subnet and named peer confs not updating. * **06.10.20:** - Disable CoreDNS in client mode, or if port 53 is already in use in server mode. diff --git a/images/docker-wireshark.md b/images/docker-wireshark.md index 3eb2f3fd8..b7a03c5c9 100644 --- a/images/docker-wireshark.md +++ b/images/docker-wireshark.md @@ -21,17 +21,17 @@ title: wireshark ## 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/wireshark` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/wireshark: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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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: wireshark: - image: lscr.io/linuxserver/wireshark + image: lscr.io/linuxserver/wireshark:latest container_name: wireshark cap_add: - NET_ADMIN @@ -87,7 +87,7 @@ docker run -d \ -p 3000:3000 `#optional` \ -v /path/to/config:/config \ --restart unless-stopped \ - lscr.io/linuxserver/wireshark + lscr.io/linuxserver/wireshark:latest ``` ## Parameters @@ -125,6 +125,12 @@ Docker images are configured using parameters passed at runtime (such as those a | Parameter | Function | | :-----: | --- | +### Portainer notice + +{% hint style="warning" %} +This image utilises `cap_add` or `sysctl` to work properly. This is not implemented properly in some versions of Portainer, thus this image may not work if deployed through Portainer. +{% endhint %} + ## Environment variables from files (Docker secrets) You can set any environment variable from a file by using a special prepend `FILE__`. @@ -170,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" }}' wireshark` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/wireshark` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/wireshark:latest` ## Versions diff --git a/images/docker-xbackbone.md b/images/docker-xbackbone.md index 6753ff866..1aad40559 100755 --- a/images/docker-xbackbone.md +++ b/images/docker-xbackbone.md @@ -21,17 +21,17 @@ title: xbackbone ## 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/xbackbone` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/xbackbone: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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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: xbackbone: - image: lscr.io/linuxserver/xbackbone + image: lscr.io/linuxserver/xbackbone:latest container_name: xbackbone environment: - PUID=1000 @@ -88,7 +88,7 @@ docker run -d \ -p 443:443 \ -v /path/to/data:/config \ --restart unless-stopped \ - lscr.io/linuxserver/xbackbone + lscr.io/linuxserver/xbackbone:latest ``` ## Parameters @@ -166,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" }}' xbackbone` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/xbackbone` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/xbackbone:latest` ## Versions diff --git a/images/docker-znc.md b/images/docker-znc.md index 56e2a39fc..50ad7fa53 100644 --- a/images/docker-znc.md +++ b/images/docker-znc.md @@ -21,17 +21,17 @@ title: znc ## 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/znc` should retrieve the correct image for your arch, but you can also pull specific arch images via tags. +Simply pulling `lscr.io/linuxserver/znc: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-\ | +| arm64 | ✅ | arm64v8-\ | +| armhf| ✅ | arm32v7-\ | ## 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: znc: - image: lscr.io/linuxserver/znc + image: lscr.io/linuxserver/znc:latest container_name: znc environment: - PUID=1000 @@ -76,7 +76,7 @@ docker run -d \ -p 6501:6501 \ -v :/config \ --restart unless-stopped \ - lscr.io/linuxserver/znc + lscr.io/linuxserver/znc: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" }}' znc` * Image version number - * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/znc` + * `docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/znc:latest` ## Versions