© Info :: LinuxServer.io, 2025 +November 9, 2025 at 4:45 PM
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡ Subscribe via RSS — to all updates
We have created a new alpine based version of our mariadb container.
-Our intent is to move :alpine tag to :latest once ready. Further info on the timeline will follow in the coming weeks.
:alpine tag to :latest once ready. Further info on the timeline will follow in the coming weeks.latest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2021-03-13-rutorrent/index.html b/issues/2021-03-13-rutorrent/index.html
index f7f7428a..3bf31224 100644
--- a/issues/2021-03-13-rutorrent/index.html
+++ b/issues/2021-03-13-rutorrent/index.html
@@ -1,5 +1,5 @@
Our ruTorrent image is being deprecated. While it will still be available, no new version will be built. We are directing anyone still interested in using rTorrent / ruTorrent in docker to crazy-max’s container. If you are interested in taking over as a maintainer, please see this issue. Our ruTorrent image is being deprecated. While it will still be available, no new version will be built. We are directing anyone still interested in using rTorrent / ruTorrent in docker to crazy-max’s container. If you are interested in taking over as a maintainer, please see this issue.ruTorrent is being deprecated
March 13, 2021 at 12:00 AMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2021-06-17-openvpn-as/index.html b/issues/2021-06-17-openvpn-as/index.html
index 5b5bb975..e71b9f35 100644
--- a/issues/2021-06-17-openvpn-as/index.html
+++ b/issues/2021-06-17-openvpn-as/index.html
@@ -1,5 +1,5 @@
Our openvpn-as image is being deprecated. While it will still be available, no new version will be built. We recommend users take a look at our wireguard image as a possible replacement. Our openvpn-as image is being deprecated. While it will still be available, no new version will be built. We recommend users take a look at our wireguard image as a possible replacement.openvpn-as is being deprecated
June 17, 2021 at 12:00 AMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2021-08-25-mariadb-alpine/index.html b/issues/2021-08-25-mariadb-alpine/index.html
index 8ed83846..a080a0da 100644
--- a/issues/2021-08-25-mariadb-alpine/index.html
+++ b/issues/2021-08-25-mariadb-alpine/index.html
@@ -2,7 +2,7 @@
If for some reason you need to remain on the old version, you can pin your install to the version-110.4.21mariabionic tag, although please be aware that no further updates will be provided for it."> As previously announced we have now moved the MariaDB If for some reason you need to remain on the old version, you can pin your install to the As previously announced we have now moved the MariaDB If for some reason you need to remain on the old version, you can pin your install to the mariadb change to Alpine
August 25, 2021 at 12:00 AM:alpine tag to :latest and deprecated our Ubuntu-based image. No user action is required when updating to the new tag, but as ever we recommend ensuring you have a proven backup of your data before performing any updates. Going forward, the :alpine tag will not receive any further updates.version-110.4.21mariabionic tag, although please be aware that no further updates will be provided for it.:alpine tag to :latest and deprecated our Ubuntu-based image. No user action is required when updating to the new tag, but as ever we recommend ensuring you have a proven backup of your data before performing any updates. Going forward, the :alpine tag will not receive any further updates.version-110.4.21mariabionic tag, although please be aware that no further updates will be provided for it.latest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2021-09-07-airsonic/index.html b/issues/2021-09-07-airsonic/index.html
index 648b7326..648730e2 100644
--- a/issues/2021-09-07-airsonic/index.html
+++ b/issues/2021-09-07-airsonic/index.html
@@ -3,7 +3,7 @@ We’re currently looking into creating an AirSonic-Advanced image and will
We’re currently looking into creating an AirSonic-Advanced image and will post an update when this has been released. For the time being we will continue to let our airsonic builds update dependencies but once airsonic-advanced is released that will be stopped."> As stated by the airsonic team here, Airsonic is now no longer maintained and is recommended to use airsonic-advanced.
-We’re currently looking into creating an AirSonic-Advanced image and will post an update when this has been released. For the time being we will continue to let our airsonic builds update dependencies but once airsonic-advanced is released that will be stopped.Airsonic Deprecation
September 7, 2021 at 12:00 AMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2021-11-25-unifi/index.html b/issues/2021-11-25-unifi/index.html
index a8ce6d86..9b63a09a 100644
--- a/issues/2021-11-25-unifi/index.html
+++ b/issues/2021-11-25-unifi/index.html
@@ -2,7 +2,7 @@
If you are currently running the Unifi Controller image on a 32 bit ARM platform we recommend you look at alternative options such as upgrading to a 64 bit OS if your hardware supports it."> Deprecations
-unifi-controller Due to a lack of upstream support for mongodb on 32 bit platforms, we have made the decision to deprecate our 32 bit ARM (also known as armhf / armv7) Unifi Controller image. We will continue to update the image until June 2022 at which point it will cease to be supported. If you are currently running the Unifi Controller image on a 32 bit ARM platform we recommend you look at alternative options such as upgrading to a 64 bit OS if your hardware supports it. Due to a lack of upstream support for mongodb on 32 bit platforms, we have made the decision to deprecate our 32 bit ARM (also known as armhf / armv7) Unifi Controller image. We will continue to update the image until June 2022 at which point it will cease to be supported. If you are currently running the Unifi Controller image on a 32 bit ARM platform we recommend you look at alternative options such as upgrading to a 64 bit OS if your hardware supports it.Unifi Controller 32-bit ARM Deprecation Notice
November 25, 2021 at 12:00 AMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2022-01-06-qbittorrent/index.html b/issues/2022-01-06-qbittorrent/index.html
index 3cf729fe..fc7d3d45 100644
--- a/issues/2022-01-06-qbittorrent/index.html
+++ b/issues/2022-01-06-qbittorrent/index.html
@@ -2,7 +2,7 @@
If you are currently running the Unstable image we recommend switching to the Stable image. If and when the upstream project start building Unstable packages for Ubuntu LTS we will look to reinstate the image."> Due to a lack of upstream support for Ubuntu LTS (Focal), we have made the decision to deprecate our qBittorrent Unstable image. Support and updates for the image will cease immediately. If you are currently running the Unstable image we recommend switching to the Stable image. If and when the upstream project start building Unstable packages for Ubuntu LTS we will look to reinstate the image. Due to a lack of upstream support for Ubuntu LTS (Focal), we have made the decision to deprecate our qBittorrent Unstable image. Support and updates for the image will cease immediately. If you are currently running the Unstable image we recommend switching to the Stable image. If and when the upstream project start building Unstable packages for Ubuntu LTS we will look to reinstate the image.qBittorrent Unstable Deprecation Notice
January 6, 2022 at 6:00 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2022-01-07-qbittorrent/index.html b/issues/2022-01-07-qbittorrent/index.html
index ffc1ed5a..620e4e8d 100644
--- a/issues/2022-01-07-qbittorrent/index.html
+++ b/issues/2022-01-07-qbittorrent/index.html
@@ -2,7 +2,7 @@
If you need to stay on the existing Ubuntu-based image with v4.3.9 of qBittorrent you may pin your install to the version-14.3.9.99202110311443-7435-01519b5e7ubuntu20.04.1 tag. Please be aware that this image will not receive any further updates."> Due to the upstream project dropping support for Ubuntu LTS (Focal) in their most recent release (v4.4.0) we have decided to switch our qBittorrent container to our Alpine baseimage. We apologise for the short notice but we didn’t have sufficient information from the upstream project to make these decisions in advance. If you need to stay on the existing Ubuntu-based image with v4.3.9 of qBittorrent you may pin your install to the This change should not affect most users, however, if you rely on custom scripts or 3rd party packages you may need to make changes to ensure they continue to function as before. Additionally - if you make use of the Due to the upstream project dropping support for Ubuntu LTS (Focal) in their most recent release (v4.4.0) we have decided to switch our qBittorrent container to our Alpine baseimage. We apologise for the short notice but we didn’t have sufficient information from the upstream project to make these decisions in advance. If you need to stay on the existing Ubuntu-based image with v4.3.9 of qBittorrent you may pin your install to the This change should not affect most users, however, if you rely on custom scripts or 3rd party packages you may need to make changes to ensure they continue to function as before. Additionally - if you make use of the qBittorrent change to Alpine
January 7, 2022 at 6:00 PMversion-14.3.9.99202110311443-7435-01519b5e7ubuntu20.04.1 tag. Please be aware that this image will not receive any further updates.qbt CLI tool - as part of this change we have switched from using https://github.com/fedarovich/qbittorrent-cli, which does not provide Alpine-compatible binaries, to https://github.com/ludviglundgren/qbittorrent-cli which does. While these tools are very similar in function, the syntax differs between them.version-14.3.9.99202110311443-7435-01519b5e7ubuntu20.04.1 tag. Please be aware that this image will not receive any further updates.qbt CLI tool - as part of this change we have switched from using https://github.com/fedarovich/qbittorrent-cli, which does not provide Alpine-compatible binaries, to https://github.com/ludviglundgren/qbittorrent-cli which does. While these tools are very similar in function, the syntax differs between them.latest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2022-01-13-airsonic/index.html b/issues/2022-01-13-airsonic/index.html
index 6df9a951..4379d321 100644
--- a/issues/2022-01-13-airsonic/index.html
+++ b/issues/2022-01-13-airsonic/index.html
@@ -2,7 +2,7 @@
Users of the image are advised to switch to our Airsonic-Advanced image instead."> Due to ending of support by the upstream project, we have made the decision to deprecate our Airsonic image. The image will immediately cease to be supported and will not receive any further updates. Users of the image are advised to switch to our Airsonic-Advanced image instead. Due to ending of support by the upstream project, we have made the decision to deprecate our Airsonic image. The image will immediately cease to be supported and will not receive any further updates. Users of the image are advised to switch to our Airsonic-Advanced image instead.Airsonic Deprecation Notice
January 13, 2022 at 6:00 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2022-01-19-clarkson/index.html b/issues/2022-01-19-clarkson/index.html
index ed3b52fa..80fe3ba4 100644
--- a/issues/2022-01-19-clarkson/index.html
+++ b/issues/2022-01-19-clarkson/index.html
@@ -2,7 +2,7 @@
Users of the image are advised to look at Hammond as a possible replacement."> Due to ending of support by the upstream project, we have made the decision to deprecate our Clarkson image. The image will immediately cease to be supported and will not receive any further updates. Users of the image are advised to look at Hammond as a possible replacement.Clarkson Deprecation Notice
January 19, 2022 at 4:00 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2022-01-25-pyload/index.html b/issues/2022-01-25-pyload/index.html
index e025a753..053e9da3 100644
--- a/issues/2022-01-25-pyload/index.html
+++ b/issues/2022-01-25-pyload/index.html
@@ -2,7 +2,7 @@
Users of the image are advised to switch to our new pyLoad-ng image as a replacement."> Due to a dependency on Python2 and Alpine 3.12, both of which are already or approaching end of support, we have made the decision to deprecate our pyLoad image. The image will immediately cease to be supported and will not receive any further updates. Users of the image are advised to switch to our new pyLoad-ng image as a replacement. Due to a dependency on Python2 and Alpine 3.12, both of which are already or approaching end of support, we have made the decision to deprecate our pyLoad image. The image will immediately cease to be supported and will not receive any further updates. Users of the image are advised to switch to our new pyLoad-ng image as a replacement.pyLoad Deprecation Notice
January 25, 2022 at 6:00 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2022-02-24-kodi-headless/index.html b/issues/2022-02-24-kodi-headless/index.html
index da6ee550..64e47945 100644
--- a/issues/2022-02-24-kodi-headless/index.html
+++ b/issues/2022-02-24-kodi-headless/index.html
@@ -2,7 +2,7 @@
Users of the image are advised to switch to this fork of the image by matthuisman instead."> Due to the lack of an active maintainer, we have made the decision to deprecate our kodi-headless image. The image will immediately cease to be supported and will not receive any further updates. Users of the image are advised to switch to this fork of the image by matthuisman instead. Due to the lack of an active maintainer, we have made the decision to deprecate our kodi-headless image. The image will immediately cease to be supported and will not receive any further updates. Users of the image are advised to switch to this fork of the image by matthuisman instead.Kodi-Headless Deprecation Notice
February 24, 2022 at 9:00 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2022-03-01-couchpotato/index.html b/issues/2022-03-01-couchpotato/index.html
index 4f74a7a5..afe0cbd3 100644
--- a/issues/2022-03-01-couchpotato/index.html
+++ b/issues/2022-03-01-couchpotato/index.html
@@ -2,7 +2,7 @@
Users of the image may wish to look at our Radarr image as an alternative."> Due to the upstream project no longer being maintained, we have made the decision to deprecate our Couchpotato image. The image will immediately cease to be supported and will not receive any further updates. Users of the image may wish to look at our Radarr image as an alternative. Due to the upstream project no longer being maintained, we have made the decision to deprecate our Couchpotato image. The image will immediately cease to be supported and will not receive any further updates. Users of the image may wish to look at our Radarr image as an alternative.Couchpotato Deprecation Notice
March 1, 2022 at 12:00 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2022-05-31-unifi-controller/index.html b/issues/2022-05-31-unifi-controller/index.html
index 10be0b70..d30d3e83 100644
--- a/issues/2022-05-31-unifi-controller/index.html
+++ b/issues/2022-05-31-unifi-controller/index.html
@@ -2,7 +2,7 @@
If you are currently running the Unifi Controller image on a 32 bit ARM platform we recommend you look at alternative options such as upgrading to a 64 bit OS if your hardware supports it."> Deprecations
-unifi-controller As per our previous announcement today sees the deprecation of the 32-bit ARM (armhf) version of our Unifi Controller image. The last functional armhf tag will be If you are currently running the Unifi Controller image on a 32 bit ARM platform we recommend you look at alternative options such as upgrading to a 64 bit OS if your hardware supports it. As per our previous announcement today sees the deprecation of the 32-bit ARM (armhf) version of our Unifi Controller image. The last functional armhf tag will be If you are currently running the Unifi Controller image on a 32 bit ARM platform we recommend you look at alternative options such as upgrading to a 64 bit OS if your hardware supports it.Unifi Controller 32-bit ARM Deprecation Notice
May 31, 2022 at 4:00 PM7.1.66-ls151.7.1.66-ls151.latest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2022-06-05-chevereto/index.html b/issues/2022-06-05-chevereto/index.html
index 218eb7eb..b417404e 100644
--- a/issues/2022-06-05-chevereto/index.html
+++ b/issues/2022-06-05-chevereto/index.html
@@ -2,7 +2,7 @@
We recommend looking at alternative images such as pixapop, piwigo, or photoshow."> Due to the ending of upstream support for the free version of Chevereto, we will shortly be deprecating our container. We recommend looking at alternative images such as pixapop, piwigo, or photoshow. Due to the ending of upstream support for the free version of Chevereto, we will shortly be deprecating our container. We recommend looking at alternative images such as pixapop, piwigo, or photoshow.Chevereto Deprecation Notice
June 5, 2022 at 6:00 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2022-06-13-scrutiny/index.html b/issues/2022-06-13-scrutiny/index.html
index 36175c3e..9d2c9a0b 100644
--- a/issues/2022-06-13-scrutiny/index.html
+++ b/issues/2022-06-13-scrutiny/index.html
@@ -2,7 +2,7 @@
We recommend switching to the official Docker images."> Due to issues maintaining parity with the upstream container releases, we are deprecating our Scrutiny container. We recommend switching to the official Docker images. Due to issues maintaining parity with the upstream container releases, we are deprecating our Scrutiny container. We recommend switching to the official Docker images.Scrutiny Deprecation Notice
June 13, 2022 at 6:00 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2022-06-20-kanzi/index.html b/issues/2022-06-20-kanzi/index.html
index 59aae07c..e5c01586 100644
--- a/issues/2022-06-20-kanzi/index.html
+++ b/issues/2022-06-20-kanzi/index.html
@@ -1,5 +1,5 @@
Due to the lack of an active maintainer, and 2 years without an upstream release, we are deprecating our Kanzi container. Due to the lack of an active maintainer, and 2 years without an upstream release, we are deprecating our Kanzi container.Kanzi Deprecation Notice
June 20, 2022 at 11:00 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2022-06-23-cloud9/index.html b/issues/2022-06-23-cloud9/index.html
index ffd4693b..b96ebd29 100644
--- a/issues/2022-06-23-cloud9/index.html
+++ b/issues/2022-06-23-cloud9/index.html
@@ -2,7 +2,7 @@
We recommend looking at our code-server and openvscode-server containers as potential replacements."> Due to the lack of upstream support and overhead maintaining our own fork of the codebase, we will shortly be deprecating our Cloud9 container. We recommend looking at our code-server and openvscode-server containers as potential replacements. Due to the lack of upstream support and overhead maintaining our own fork of the codebase, we will shortly be deprecating our Cloud9 container. We recommend looking at our code-server and openvscode-server containers as potential replacements.Cloud9 Deprecation Notice
June 23, 2022 at 4:00 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2022-08-02-duplicati/index.html b/issues/2022-08-02-duplicati/index.html
index 2ef62a0e..3449c8d4 100644
--- a/issues/2022-08-02-duplicati/index.html
+++ b/issues/2022-08-02-duplicati/index.html
@@ -5,7 +5,7 @@ The last supported tags for 32-bit ARM will be v2.0.6.3-2.0.6.3_beta_2021-06-17-
If you are currently running the Duplicati image on a 32-bit ARM platform we recommend you look at alternative options such as upgrading to a 64-bit OS if your hardware supports it. Please see our blog post regarding our support policy for armhf."> Due to the lack of reliable support for Mono on 32-bit ARM, we will shortly be deprecating the 32-bit ARM (armhf) version of our Duplicati container. The last supported tags for 32-bit ARM will be If you are currently running the Duplicati image on a 32-bit ARM platform we recommend you look at alternative options such as upgrading to a 64-bit OS if your hardware supports it. Please see our blog post regarding our support policy for armhf. Due to the lack of reliable support for Mono on 32-bit ARM, we will shortly be deprecating the 32-bit ARM (armhf) version of our Duplicati container. The last supported tags for 32-bit ARM will be If you are currently running the Duplicati image on a 32-bit ARM platform we recommend you look at alternative options such as upgrading to a 64-bit OS if your hardware supports it. Please see our blog post regarding our support policy for armhf.Duplicati 32-bit ARM Deprecation Notice
August 2, 2022 at 10:00 PMv2.0.6.3-2.0.6.3_beta_2021-06-17-ls135 for the stable branch and development-v2.0.6.104-2.0.6.104_canary_2022-06-15-ls89 for the development branch.v2.0.6.3-2.0.6.3_beta_2021-06-17-ls135 for the stable branch and development-v2.0.6.104-2.0.6.104_canary_2022-06-15-ls89 for the development branch.latest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2022-08-02-sonarr/index.html b/issues/2022-08-02-sonarr/index.html
index da1219e2..8cec4934 100644
--- a/issues/2022-08-02-sonarr/index.html
+++ b/issues/2022-08-02-sonarr/index.html
@@ -5,7 +5,7 @@ The last supported tags for 32-bit ARM will be 3.0.8.1507-ls151 for the stable b
If you are currently running the Sonarr image on a 32-bit ARM platform we recommend you look at alternative options such as upgrading to a 64-bit OS if your hardware supports it. Please see our blog post regarding our support policy for armhf."> Due to the lack of reliable support for Mono on 32-bit ARM, we will shortly be deprecating the 32-bit ARM (armhf) version of our Sonarr container. The last supported tags for 32-bit ARM will be If you are currently running the Sonarr image on a 32-bit ARM platform we recommend you look at alternative options such as upgrading to a 64-bit OS if your hardware supports it. Please see our blog post regarding our support policy for armhf. Due to the lack of reliable support for Mono on 32-bit ARM, we will shortly be deprecating the 32-bit ARM (armhf) version of our Sonarr container. The last supported tags for 32-bit ARM will be If you are currently running the Sonarr image on a 32-bit ARM platform we recommend you look at alternative options such as upgrading to a 64-bit OS if your hardware supports it. Please see our blog post regarding our support policy for armhf.Sonarr 32-bit ARM Deprecation Notice
August 2, 2022 at 10:00 PM3.0.8.1507-ls151 for the stable branch and develop-3.0.8.1540-ls294 for the develop branch.3.0.8.1507-ls151 for the stable branch and develop-3.0.8.1540-ls294 for the develop branch.latest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2022-09-05-paperless-ng/index.html b/issues/2022-09-05-paperless-ng/index.html
index 11786c15..576ad722 100644
--- a/issues/2022-09-05-paperless-ng/index.html
+++ b/issues/2022-09-05-paperless-ng/index.html
@@ -2,7 +2,7 @@
We recommend switching to the new forks official container Paperless-ngx"> Due to the upstream project no longer being in development, we are deprecating our Paperless-ng container. We recommend switching to the new forks official container Paperless-ngx Due to the upstream project no longer being in development, we are deprecating our Paperless-ng container. We recommend switching to the new forks official container Paperless-ngxPaperless-ng Deprecation Notice
September 5, 2022 at 6:00 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2022-09-05-paperless-ngx/index.html b/issues/2022-09-05-paperless-ngx/index.html
index 9eccadb2..19760926 100644
--- a/issues/2022-09-05-paperless-ngx/index.html
+++ b/issues/2022-09-05-paperless-ngx/index.html
@@ -5,7 +5,7 @@ We recommend switching to their official container Paperless-ngx
While the volume mounts are different, it should be a drop-in replacement."> Due to issues maintaining parity with the upstream container releases, we are deprecating our Paperless-ng container. We recommend switching to their official container Paperless-ngx While the volume mounts are different, it should be a drop-in replacement. Due to issues maintaining parity with the upstream container releases, we are deprecating our Paperless-ng container. We recommend switching to their official container Paperless-ngx While the volume mounts are different, it should be a drop-in replacement.Paperless-ngx Deprecation Notice
September 5, 2022 at 6:00 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2022-10-14-photoshow/index.html b/issues/2022-10-14-photoshow/index.html
index 598b9a73..9ed17418 100644
--- a/issues/2022-10-14-photoshow/index.html
+++ b/issues/2022-10-14-photoshow/index.html
@@ -1,5 +1,5 @@
Due to the upstream project no longer being in development, we are deprecating our PhotoShow container. Due to the upstream project no longer being in development, we are deprecating our PhotoShow container.PhotoShow Deprecation Notice
October 14, 2022 at 12:00 AMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2022-10-14-pixapop/index.html b/issues/2022-10-14-pixapop/index.html
index 18f2115c..c9d18a8e 100644
--- a/issues/2022-10-14-pixapop/index.html
+++ b/issues/2022-10-14-pixapop/index.html
@@ -1,5 +1,5 @@
Due to the upstream project no longer being in development, we are deprecating our Pixapop container. Due to the upstream project no longer being in development, we are deprecating our Pixapop container.Pixapop Deprecation Notice
October 14, 2022 at 12:00 AMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2022-10-21-muximux/index.html b/issues/2022-10-21-muximux/index.html
index 83730142..4bead1ae 100644
--- a/issues/2022-10-21-muximux/index.html
+++ b/issues/2022-10-21-muximux/index.html
@@ -1,5 +1,5 @@
Due to the upstream project no longer being in development, we are deprecating our Muximux container. Due to the upstream project no longer being in development, we are deprecating our Muximux container.Muximux Deprecation Notice
October 21, 2022 at 12:00 AMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2022-10-24-nextcloud/index.html b/issues/2022-10-24-nextcloud/index.html
index 85217fb8..6c365124 100644
--- a/issues/2022-10-24-nextcloud/index.html
+++ b/issues/2022-10-24-nextcloud/index.html
@@ -1,5 +1,5 @@
We are deprecating the We are deprecating the Nextcloud php8 Tag Deprecation Notice
October 25, 2022 at 8:00 PMphp8 tag/branch of our Nextcloud container. The latest tag (master branch) now uses php8.php8 tag/branch of our Nextcloud container. The latest tag (master branch) now uses php8.latest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2022-11-27-nzbget/index.html b/issues/2022-11-27-nzbget/index.html
index a849372a..20a89f89 100644
--- a/issues/2022-11-27-nzbget/index.html
+++ b/issues/2022-11-27-nzbget/index.html
@@ -2,7 +2,7 @@
Please consider switching to SABnzbd."> Due to the upstream project no longer being in development, we will be deprecating our nzbget container on December 31, 2022. Please consider switching to SABnzbd. Due to the upstream project no longer being in development, we will be deprecating our nzbget container on December 31, 2022. Please consider switching to SABnzbd.nzbget Deprecation Notice
November 27, 2022 at 11:59 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2022-12-26-booksonic-air/index.html b/issues/2022-12-26-booksonic-air/index.html
index a1ca4f8b..0d9946b5 100644
--- a/issues/2022-12-26-booksonic-air/index.html
+++ b/issues/2022-12-26-booksonic-air/index.html
@@ -5,7 +5,7 @@ The last supported tag for 32-bit ARM will be v2201.1.0-ls77.
If you are currently running the Booksonic Air image on a 32-bit ARM platform we recommend you look at alternative options such as upgrading to a 64-bit OS if your hardware supports it. Please see our blog post regarding our support policy for armhf."> Due to the lack of support for modern Java runtime packages on 32-bit ARM from the Alpine repos, we will shortly be deprecating the 32-bit ARM (armhf) version of our Booksonic Air image. The last supported tag for 32-bit ARM will be If you are currently running the Booksonic Air image on a 32-bit ARM platform we recommend you look at alternative options such as upgrading to a 64-bit OS if your hardware supports it. Please see our blog post regarding our support policy for armhf. Due to the lack of support for modern Java runtime packages on 32-bit ARM from the Alpine repos, we will shortly be deprecating the 32-bit ARM (armhf) version of our Booksonic Air image. The last supported tag for 32-bit ARM will be If you are currently running the Booksonic Air image on a 32-bit ARM platform we recommend you look at alternative options such as upgrading to a 64-bit OS if your hardware supports it. Please see our blog post regarding our support policy for armhf.Booksonic Air 32-bit ARM Deprecation Notice
December 26, 2022 at 12:00 PMv2201.1.0-ls77.v2201.1.0-ls77.latest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2023-01-19-nzbget/index.html b/issues/2023-01-19-nzbget/index.html
index 6713a632..39332815 100644
--- a/issues/2023-01-19-nzbget/index.html
+++ b/issues/2023-01-19-nzbget/index.html
@@ -8,7 +8,7 @@ Please consider switching to SABnzbd."> Follow up for https://info.linuxserver.io/issues/2022-11-27-nzbget/ Due to the upstream project no longer being in development, we are deprecating our nzbget container. We are monitoring activity of forks of the original nzbget and may release a separate image if a viable option presents itself. Please consider switching to SABnzbd. Follow up for https://info.linuxserver.io/issues/2022-11-27-nzbget/ Due to the upstream project no longer being in development, we are deprecating our nzbget container. We are monitoring activity of forks of the original nzbget and may release a separate image if a viable option presents itself. Please consider switching to SABnzbd.nzbget Deprecation Notice
January 19, 2023 at 11:59 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2023-01-22-nzbhydra2/index.html b/issues/2023-01-22-nzbhydra2/index.html
index de131360..c8309c1a 100644
--- a/issues/2023-01-22-nzbhydra2/index.html
+++ b/issues/2023-01-22-nzbhydra2/index.html
@@ -5,7 +5,7 @@ We will announce the last supported tag for 32-bit ARM at that time.
If you are currently running the nzbhydra2 image on a 32-bit ARM platform we recommend you look at alternative options such as upgrading to a 64-bit OS if your hardware supports it. Please see our blog post regarding our support policy for armhf."> Due to the lack of upstream packages for 32-bit ARM preventing improvements to the image, we will be deprecating the 32-bit ARM (armhf) version of our nzbhydra2 image on 2023-03-31. We will announce the last supported tag for 32-bit ARM at that time. If you are currently running the nzbhydra2 image on a 32-bit ARM platform we recommend you look at alternative options such as upgrading to a 64-bit OS if your hardware supports it. Please see our blog post regarding our support policy for armhf. Due to the lack of upstream packages for 32-bit ARM preventing improvements to the image, we will be deprecating the 32-bit ARM (armhf) version of our nzbhydra2 image on 2023-03-31. We will announce the last supported tag for 32-bit ARM at that time. If you are currently running the nzbhydra2 image on a 32-bit ARM platform we recommend you look at alternative options such as upgrading to a 64-bit OS if your hardware supports it. Please see our blog post regarding our support policy for armhf.nzbhydra2 32-bit ARM Deprecation Notice
January 22, 2023 at 10:00 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2023-02-15-guacd/index.html b/issues/2023-02-15-guacd/index.html
index e34d7b48..e932d372 100644
--- a/issues/2023-02-15-guacd/index.html
+++ b/issues/2023-02-15-guacd/index.html
@@ -2,7 +2,7 @@
We recommend switching to their official container, though please note this only offers support for amd64 platforms."> Due to a lack of upstream support for modern dependencies, we are deprecating our guacd container. We recommend switching to their official container, though please note this only offers support for amd64 platforms. Due to a lack of upstream support for modern dependencies, we are deprecating our guacd container. We recommend switching to their official container, though please note this only offers support for amd64 platforms.guacd Deprecation Notice
February 15, 2023 at 3:00 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2023-02-15-papermerge/index.html b/issues/2023-02-15-papermerge/index.html
index b66644fe..585f2571 100644
--- a/issues/2023-02-15-papermerge/index.html
+++ b/issues/2023-02-15-papermerge/index.html
@@ -5,7 +5,7 @@ We recommend switching to their official container.
Their documentation can be found here."> Due to issues maintaining parity with the upstream container releases, we are deprecating our Papermerge container. We recommend switching to their official container. Their documentation can be found here. Due to issues maintaining parity with the upstream container releases, we are deprecating our Papermerge container. We recommend switching to their official container. Their documentation can be found here.Papermerge Deprecation Notice
February 15, 2023 at 3:00 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2023-02-16-docker-compose/index.html b/issues/2023-02-16-docker-compose/index.html
index 191e69ab..5263ba94 100644
--- a/issues/2023-02-16-docker-compose/index.html
+++ b/issues/2023-02-16-docker-compose/index.html
@@ -5,7 +5,7 @@ Docker Compose is now available from the official Docker repos.
Current and previous releases can also be downloaded directly from their GitHub repo."> Due to changes is upstream distribution, we are deprecating our Docker Compose container. Docker Compose is now available from the official Docker repos. Current and previous releases can also be downloaded directly from their GitHub repo. Due to changes is upstream distribution, we are deprecating our Docker Compose container. Docker Compose is now available from the official Docker repos. Current and previous releases can also be downloaded directly from their GitHub repo.Docker Compose Deprecation Notice
February 16, 2023 at 3:00 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2023-02-25-tvheadend/index.html b/issues/2023-02-25-tvheadend/index.html
index 4bb322dd..7e6c3102 100644
--- a/issues/2023-02-25-tvheadend/index.html
+++ b/issues/2023-02-25-tvheadend/index.html
@@ -5,7 +5,7 @@ The last supported tags for 32-bit ARM will be 02987438-ls151.
If you are currently running the TVheadend image on a 32-bit ARM platform we recommend you look at alternative options such as upgrading to a 64-bit OS if your hardware supports it. Please see our blog post regarding our support policy for armhf."> Due to build issues on 32-bit ARM, we are deprecating the 32-bit ARM (armhf) version of our TVheadend container. The last supported tags for 32-bit ARM will be If you are currently running the TVheadend image on a 32-bit ARM platform we recommend you look at alternative options such as upgrading to a 64-bit OS if your hardware supports it. Please see our blog post regarding our support policy for armhf. Due to build issues on 32-bit ARM, we are deprecating the 32-bit ARM (armhf) version of our TVheadend container. The last supported tags for 32-bit ARM will be If you are currently running the TVheadend image on a 32-bit ARM platform we recommend you look at alternative options such as upgrading to a 64-bit OS if your hardware supports it. Please see our blog post regarding our support policy for armhf.TVheadend 32-bit ARM Deprecation Notice
February 25, 2023 at 6:00 PM02987438-ls151.02987438-ls151.latest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2023-04-06-armhf/index.html b/issues/2023-04-06-armhf/index.html
index 826d7076..fef2ef9e 100644
--- a/issues/2023-04-06-armhf/index.html
+++ b/issues/2023-04-06-armhf/index.html
@@ -2,7 +2,7 @@
Please read our blog post on the matter for more details."> Due to the ever-decreasing support for modern apps and packages on 32-bit Arm platforms, we will be deprecating all 32-bit Arm (armhf) versions of our images effective 2023-07-01. Please read our blog post on the matter for more details. Due to the ever-decreasing support for modern apps and packages on 32-bit Arm platforms, we will be deprecating all 32-bit Arm (armhf) versions of our images effective 2023-07-01. Please read our blog post on the matter for more details.32-bit Arm Deprecation Notice
April 6, 2023 at 6:00 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2023-04-13-calibre-web/index.html b/issues/2023-04-13-calibre-web/index.html
index 8a594e67..74585f79 100644
--- a/issues/2023-04-13-calibre-web/index.html
+++ b/issues/2023-04-13-calibre-web/index.html
@@ -5,7 +5,7 @@ The last supported tag for 32-bit Arm will be 0.6.20-ls204 for the stable branch
If you are currently running the Calibre-Web image on a 32-bit Arm platform we recommend you look at alternative options such as upgrading to a 64-bit OS if your hardware supports it. Please see our blog post regarding our support policy for armhf."> Due to issues building required dependencies on 32-bit Arm, we have taken the decision to deprecate the 32-bit Arm (armhf) version of our Calibre-Web image. The last supported tag for 32-bit Arm will be If you are currently running the Calibre-Web image on a 32-bit Arm platform we recommend you look at alternative options such as upgrading to a 64-bit OS if your hardware supports it. Please see our blog post regarding our support policy for armhf. Due to issues building required dependencies on 32-bit Arm, we have taken the decision to deprecate the 32-bit Arm (armhf) version of our Calibre-Web image. The last supported tag for 32-bit Arm will be If you are currently running the Calibre-Web image on a 32-bit Arm platform we recommend you look at alternative options such as upgrading to a 64-bit OS if your hardware supports it. Please see our blog post regarding our support policy for armhf.Calibre-Web 32-bit ARM Deprecation Notice
April 13, 2023 at 8:00 PM0.6.20-ls204 for the stable branch and nightly-6c6841f8-ls67 for nightly.0.6.20-ls204 for the stable branch and nightly-6c6841f8-ls67 for nightly.latest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2023-05-03-homeassistant/index.html b/issues/2023-05-03-homeassistant/index.html
index 961f0f8a..77b20810 100644
--- a/issues/2023-05-03-homeassistant/index.html
+++ b/issues/2023-05-03-homeassistant/index.html
@@ -5,7 +5,7 @@ The last supported tags for 32-bit ARM will be 2023.4.6-ls141.
If you are currently running the Home Assistant image on a 32-bit ARM platform we recommend you look at alternative options such as upgrading to a 64-bit OS if your hardware supports it. Please see our blog post regarding our support policy for armhf."> Due to build issues on 32-bit ARM, we are deprecating the 32-bit ARM (armhf) version of our Home Assistant container. The last supported tags for 32-bit ARM will be If you are currently running the Home Assistant image on a 32-bit ARM platform we recommend you look at alternative options such as upgrading to a 64-bit OS if your hardware supports it. Please see our blog post regarding our support policy for armhf. Due to build issues on 32-bit ARM, we are deprecating the 32-bit ARM (armhf) version of our Home Assistant container. The last supported tags for 32-bit ARM will be If you are currently running the Home Assistant image on a 32-bit ARM platform we recommend you look at alternative options such as upgrading to a 64-bit OS if your hardware supports it. Please see our blog post regarding our support policy for armhf.Home Assistant 32-bit ARM Deprecation Notice
May 3, 2023 at 6:00 PM2023.4.6-ls141.2023.4.6-ls141.latest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2023-05-06-armhf/index.html b/issues/2023-05-06-armhf/index.html
index ce316f55..912a182f 100644
--- a/issues/2023-05-06-armhf/index.html
+++ b/issues/2023-05-06-armhf/index.html
@@ -2,7 +2,7 @@
Please read our blog post on the matter for more details."> Due to the ever-decreasing support for modern apps and packages on 32-bit Arm platforms, we will be deprecating all 32-bit Arm (armhf) versions of our images effective 2023-07-01. Please read our blog post on the matter for more details. Due to the ever-decreasing support for modern apps and packages on 32-bit Arm platforms, we will be deprecating all 32-bit Arm (armhf) versions of our images effective 2023-07-01. Please read our blog post on the matter for more details.Reminder: 32-bit Arm Deprecation Notice
May 6, 2023 at 6:00 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2023-05-15-cops/index.html b/issues/2023-05-15-cops/index.html
index d835a4a1..65514dcc 100644
--- a/issues/2023-05-15-cops/index.html
+++ b/issues/2023-05-15-cops/index.html
@@ -1,5 +1,5 @@
Due to numerous compatibility issues caused by the upstream project being abandoned and no actively maintained fork existing, we are deprecating our COPS container. Due to numerous compatibility issues caused by the upstream project being abandoned and no actively maintained fork existing, we are deprecating our COPS container.COPS Deprecation Notice
May 15, 2023 at 3:00 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2023-06-06-armhf/index.html b/issues/2023-06-06-armhf/index.html
index a4fc25d4..1d45df9e 100644
--- a/issues/2023-06-06-armhf/index.html
+++ b/issues/2023-06-06-armhf/index.html
@@ -2,7 +2,7 @@
Please read our blog post on the matter for more details."> Due to the ever-decreasing support for modern apps and packages on 32-bit Arm platforms, we will be deprecating all 32-bit Arm (armhf) versions of our images effective 2023-07-01. Please read our blog post on the matter for more details. Due to the ever-decreasing support for modern apps and packages on 32-bit Arm platforms, we will be deprecating all 32-bit Arm (armhf) versions of our images effective 2023-07-01. Please read our blog post on the matter for more details.Reminder: 32-bit Arm Deprecation Notice
June 6, 2023 at 6:00 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2023-07-01-armhf/index.html b/issues/2023-07-01-armhf/index.html
index 6864562c..13939f32 100644
--- a/issues/2023-07-01-armhf/index.html
+++ b/issues/2023-07-01-armhf/index.html
@@ -2,7 +2,7 @@
Old images will continue to work, but will not receive application or OS updates, and we will not provide support for them. Additionally, the latest and arm32v7-latest tags will no longer work for 32-bit Arm, you will need to provide a specific version tag if you wish to pull one of the old images."> As we previously announced, due to the ever-decreasing support for modern apps and packages on 32-bit Arm platforms, we have now deprecated all 32-bit Arm (armhf) versions of our images effective today, 2023-07-01. Old images will continue to work, but will not receive application or OS updates, and we will not provide support for them. Additionally, the Due to the number of images and how our build pipelines work it may take several days for the builds to complete and documentation to update to reflect the changes. Please read our blog post on the matter for more details. As we previously announced, due to the ever-decreasing support for modern apps and packages on 32-bit Arm platforms, we have now deprecated all 32-bit Arm (armhf) versions of our images effective today, 2023-07-01. Old images will continue to work, but will not receive application or OS updates, and we will not provide support for them. Additionally, the Due to the number of images and how our build pipelines work it may take several days for the builds to complete and documentation to update to reflect the changes. Please read our blog post on the matter for more details.32-bit Arm Deprecation Notice
July 1, 2023 at 12:00 PMlatest and arm32v7-latest tags will no longer work for 32-bit Arm, you will need to provide a specific version tag if you wish to pull one of the old images.latest and arm32v7-latest tags will no longer work for 32-bit Arm, you will need to provide a specific version tag if you wish to pull one of the old images.latest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2023-07-24-nano/index.html b/issues/2023-07-24-nano/index.html
index 35887a6c..32a96ff3 100644
--- a/issues/2023-07-24-nano/index.html
+++ b/issues/2023-07-24-nano/index.html
@@ -1,5 +1,5 @@
Due to issues with maintaining security updates for our private Nano network, we have decided to shut down our forked network. This includes the archival of code related to its suite of accompanying images for nano, nano-wallet, and nano-discord-bot. The web wallet which seems to be still functional when connected to an RPC server will stay online for the forseeable future. Due to issues with maintaining security updates for our private Nano network, we have decided to shut down our forked network. This includes the archival of code related to its suite of accompanying images for nano, nano-wallet, and nano-discord-bot. The web wallet which seems to be still functional when connected to an RPC server will stay online for the forseeable future.Nano Deprecation Notice
July 24, 2023 at 3:00 AMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2023-09-06-unifi-controller/index.html b/issues/2023-09-06-unifi-controller/index.html
index e3d09685..2c7278be 100644
--- a/issues/2023-09-06-unifi-controller/index.html
+++ b/issues/2023-09-06-unifi-controller/index.html
@@ -3,7 +3,7 @@ As a result we have decided to deprecate our Unifi Controller container and repl
As a result we have decided to deprecate our Unifi Controller container and replace it with a new Unifi Network Application container. This new container uses our current base images and a separate mongodb instance, which makes it substantially easier for us to maintain going forward."> Deprecations
unifi-controller
-unifi-network-application Due to the way in which Ubiquiti package and distribute their software our Unifi Controller container has reached a point where we cannot upgrade to newer supported packages without making breaking changes to the image. As a result we have decided to deprecate our Unifi Controller container and replace it with a new Unifi Network Application container. This new container uses our current base images and a separate mongodb instance, which makes it substantially easier for us to maintain going forward. We will continue to support our Unifi Controller image until 2024-01-01, at which point you will need to have migrated to the Unifi Network Application container to continue to receive support. Those of you who have been using our Due to the way in which Ubiquiti package and distribute their software our Unifi Controller container has reached a point where we cannot upgrade to newer supported packages without making breaking changes to the image. As a result we have decided to deprecate our Unifi Controller container and replace it with a new Unifi Network Application container. This new container uses our current base images and a separate mongodb instance, which makes it substantially easier for us to maintain going forward. We will continue to support our Unifi Controller image until 2024-01-01, at which point you will need to have migrated to the Unifi Network Application container to continue to receive support. Those of you who have been using our Unifi Controller Deprecation Notice
September 6, 2023 at 9:00 PMThe new container is not a drop-in replacement and it is crucial that you read the entire Application Setup section of the readme before attempting to migrate an existing install
mongoless tag for the Unifi Controller container can switch directly to the Unifi Network Application container without needing to perform any migration steps.The new container is not a drop-in replacement and it is crucial that you read the entire Application Setup section of the readme before attempting to migrate an existing install
mongoless tag for the Unifi Controller container can switch directly to the Unifi Network Application container without needing to perform any migration steps.latest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2023-10-17-headphones/index.html b/issues/2023-10-17-headphones/index.html
index 1436c3c7..84c6c24a 100644
--- a/issues/2023-10-17-headphones/index.html
+++ b/issues/2023-10-17-headphones/index.html
@@ -1,5 +1,5 @@
Due to compatibility and build issues caused by a lack of upstream development, we have decided to deprecate our Headphones container. Due to compatibility and build issues caused by a lack of upstream development, we have decided to deprecate our Headphones container.Headphones Deprecation Notice
October 17, 2023 at 9:00 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2023-10-25-embystat/index.html b/issues/2023-10-25-embystat/index.html
index c7ec2459..9edcdbc7 100644
--- a/issues/2023-10-25-embystat/index.html
+++ b/issues/2023-10-25-embystat/index.html
@@ -1,5 +1,5 @@
Due to upstream project no longer being actively developed per this update, we have decided to deprecate our EmbyStat container. Due to upstream project no longer being actively developed per this update, we have decided to deprecate our EmbyStat container.EmbyStat Deprecation Notice
October 25, 2023 at 9:00 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2023-11-12-unifi-controller/index.html b/issues/2023-11-12-unifi-controller/index.html
index 48c685e9..f4c0b36e 100644
--- a/issues/2023-11-12-unifi-controller/index.html
+++ b/issues/2023-11-12-unifi-controller/index.html
@@ -3,7 +3,7 @@ As a result we have decided to deprecate our Unifi Controller container and repl
As a result we have decided to deprecate our Unifi Controller container and replace it with a new Unifi Network Application container. This new container uses our current base images and a separate mongodb instance, which makes it substantially easier for us to maintain going forward."> Deprecations
unifi-controller
-unifi-network-application As we previously announced, due to the way in which Ubiquiti package and distribute their software our Unifi Controller container has reached a point where we cannot upgrade to newer supported packages without making breaking changes to the image. As a result we have decided to deprecate our Unifi Controller container and replace it with a new Unifi Network Application container. This new container uses our current base images and a separate mongodb instance, which makes it substantially easier for us to maintain going forward. We will continue to support our Unifi Controller image until 2024-01-01, at which point you will need to have migrated to the Unifi Network Application container to continue to receive support. Those of you who have been using our As we previously announced, due to the way in which Ubiquiti package and distribute their software our Unifi Controller container has reached a point where we cannot upgrade to newer supported packages without making breaking changes to the image. As a result we have decided to deprecate our Unifi Controller container and replace it with a new Unifi Network Application container. This new container uses our current base images and a separate mongodb instance, which makes it substantially easier for us to maintain going forward. We will continue to support our Unifi Controller image until 2024-01-01, at which point you will need to have migrated to the Unifi Network Application container to continue to receive support. Those of you who have been using our Unifi Controller Deprecation Reminder
November 12, 2023 at 9:00 PMThe new container is not a drop-in replacement and it is crucial that you read the entire Application Setup section of the readme before attempting to migrate an existing install
mongoless tag for the Unifi Controller container can switch directly to the Unifi Network Application container without needing to perform any migration steps.The new container is not a drop-in replacement and it is crucial that you read the entire Application Setup section of the readme before attempting to migrate an existing install
mongoless tag for the Unifi Controller container can switch directly to the Unifi Network Application container without needing to perform any migration steps.latest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2023-11-29-domoticz/index.html b/issues/2023-11-29-domoticz/index.html
index ca6b3e60..d22bd707 100644
--- a/issues/2023-11-29-domoticz/index.html
+++ b/issues/2023-11-29-domoticz/index.html
@@ -1,5 +1,5 @@
Due to upstream project being unwilling to build against a supported version of openssl, we have decided to deprecate our domoticz container. Due to upstream project being unwilling to build against a supported version of openssl, we have decided to deprecate our domoticz container.Domoticz Deprecation Notice
November 29, 2023 at 9:00 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2024-01-01-unifi-controller/index.html b/issues/2024-01-01-unifi-controller/index.html
index 0b73c0f3..5595766d 100644
--- a/issues/2024-01-01-unifi-controller/index.html
+++ b/issues/2024-01-01-unifi-controller/index.html
@@ -3,7 +3,7 @@ As a result we have now deprecated our Unifi Controller container and replaced i
As a result we have now deprecated our Unifi Controller container and replaced it with a new Unifi Network Application container. This new container uses our current base images and a separate mongodb instance, which makes it substantially easier for us to maintain going forward."> Deprecations
unifi-controller
-unifi-network-application As we previously announced, due to the way in which Ubiquiti package and distribute their software our Unifi Controller container has reached a point where we cannot upgrade to newer supported packages without making breaking changes to the image. As a result we have now deprecated our Unifi Controller container and replaced it with a new Unifi Network Application container. This new container uses our current base images and a separate mongodb instance, which makes it substantially easier for us to maintain going forward. Those of you who have been using our As we previously announced, due to the way in which Ubiquiti package and distribute their software our Unifi Controller container has reached a point where we cannot upgrade to newer supported packages without making breaking changes to the image. As a result we have now deprecated our Unifi Controller container and replaced it with a new Unifi Network Application container. This new container uses our current base images and a separate mongodb instance, which makes it substantially easier for us to maintain going forward. Those of you who have been using our Unifi Controller Deprecation
January 1, 2024 at 6:00 PMThe new container is not a drop-in replacement and it is crucial that you read the entire Application Setup section of the readme before attempting to migrate an existing install
mongoless tag for the Unifi Controller container can switch directly to the Unifi Network Application container without needing to perform any migration steps.The new container is not a drop-in replacement and it is crucial that you read the entire Application Setup section of the readme before attempting to migrate an existing install
mongoless tag for the Unifi Controller container can switch directly to the Unifi Network Application container without needing to perform any migration steps.latest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2024-03-20-dillinger/index.html b/issues/2024-03-20-dillinger/index.html
index 606d8509..22f97d76 100644
--- a/issues/2024-03-20-dillinger/index.html
+++ b/issues/2024-03-20-dillinger/index.html
@@ -1,5 +1,5 @@
Due to a lack of upstream development, we have decided to deprecate our dillinger container. Due to a lack of upstream development, we have decided to deprecate our dillinger container.Dillinger Deprecation Notice
March 20, 2024 at 10:00 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2024-03-21-endlessh/index.html b/issues/2024-03-21-endlessh/index.html
index 47145a9f..19afa946 100644
--- a/issues/2024-03-21-endlessh/index.html
+++ b/issues/2024-03-21-endlessh/index.html
@@ -1,5 +1,5 @@
Due to a lack of upstream development, we have decided to deprecate our endlessh container. Due to a lack of upstream development, we have decided to deprecate our endlessh container.endlessh Deprecation Notice
March 21, 2024 at 4:00 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2024-04-22-plex-meta-manager/index.html b/issues/2024-04-22-plex-meta-manager/index.html
index 114fb606..0ca71c7f 100644
--- a/issues/2024-04-22-plex-meta-manager/index.html
+++ b/issues/2024-04-22-plex-meta-manager/index.html
@@ -1,5 +1,5 @@
Deprecations
-plex-meta-manager Due to the upstream project rebranding, we have decided to deprecate our Plex Meta Manager container. Please migrate to our new Kometa image instead. Due to the upstream project rebranding, we have decided to deprecate our Plex Meta Manager container. Please migrate to our new Kometa image instead.Plex Meta Manager Deprecation Notice
April 23, 2024 at 12:00 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2024-07-16-wireguard/index.html b/issues/2024-07-16-wireguard/index.html
index 1f861614..940d313f 100644
--- a/issues/2024-07-16-wireguard/index.html
+++ b/issues/2024-07-16-wireguard/index.html
@@ -1,5 +1,5 @@
A little over a year ago we updated our default Wireguard image to no longer support building the Wireguard kernel modules and moved that functionality to the Revisiting the situation now we see that the vast majority of users are now either running a kernel with built-in Wireguard support or a custom kernel, such as on a VPS or NAS, which we have never supported building for. As a result we have decided to deprecate the In practice this means there’s only one case where there will be a still-supported kernel version that doesn’t have built-in Wireguard support: 4.19, which goes EOL at the end of 2025. Our stats show a tiny handful of users that this applies to. If you are still running a 4.19 kernel, or are running any other EOL pre-5.6 kernel, and for whatever reason cannot upgrade then your only option will be to build the Wireguard kernel modules on the host, which the default image (using the We will provide additional reminders of this deprecation towards the end of the year. A little over a year ago we updated our default Wireguard image to no longer support building the Wireguard kernel modules and moved that functionality to the Revisiting the situation now we see that the vast majority of users are now either running a kernel with built-in Wireguard support or a custom kernel, such as on a VPS or NAS, which we have never supported building for. As a result we have decided to deprecate the In practice this means there’s only one case where there will be a still-supported kernel version that doesn’t have built-in Wireguard support: 4.19, which goes EOL at the end of 2025. Our stats show a tiny handful of users that this applies to. If you are still running a 4.19 kernel, or are running any other EOL pre-5.6 kernel, and for whatever reason cannot upgrade then your only option will be to build the Wireguard kernel modules on the host, which the default image (using the We will provide additional reminders of this deprecation towards the end of the year.Wireguard Legacy Tag Deprecation
July 16, 2024 at 6:00 PMlegacy tag. We did this on the basis that most users were running a kernel that already had built-in Wireguard support (5.6 or above in terms of official kernel releases) and this allowed us to reduce the size of the default image by 600Mb for them.legacy tag from the end of 2024.latest tag) will then be able to make use of.legacy tag. We did this on the basis that most users were running a kernel that already had built-in Wireguard support (5.6 or above in terms of official kernel releases) and this allowed us to reduce the size of the default image by 600Mb for them.legacy tag from the end of 2024.latest tag) will then be able to make use of.latest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.
© Info :: LinuxServer.io, 2025 • Back to top
LinuxServer.io Status page
Powered by cState⚡
Subscribe via RSS —
diff --git a/issues/2024-08-11-deprecation-changes/index.html b/issues/2024-08-11-deprecation-changes/index.html
index 038e9ae8..b80abf5e 100644
--- a/issues/2024-08-11-deprecation-changes/index.html
+++ b/issues/2024-08-11-deprecation-changes/index.html
@@ -1,4 +1,4 @@
- Currently, when we deprecate an image, we add a note to the readme and to the startup logs to make users aware that the image is no longer actively supported and will not receive further updates. Users can then make their own decision as to whether to continue using it or not. Despite this, we still see a significant number of pulls for images that we have long since stopped updating, primarily because users don’t read the notices, or use a container management platform that doesn’t expose them. Wherever possible we want to avoid actually removing images from registries, because it can prevent legitimate uses of them & because we feel it goes against the open source philosophy, so to try and reduce the number of users setting up new instances with unsupported and outdated images, we are changing our deprecation process. Going forward, when we deprecate an image, we will be pushing an empty index for the Currently, when we deprecate an image, we add a note to the readme and to the startup logs to make users aware that the image is no longer actively supported and will not receive further updates. Users can then make their own decision as to whether to continue using it or not. Despite this, we still see a significant number of pulls for images that we have long since stopped updating, primarily because users don’t read the notices, or use a container management platform that doesn’t expose them. Wherever possible we want to avoid actually removing images from registries, because it can prevent legitimate uses of them & because we feel it goes against the open source philosophy, so to try and reduce the number of users setting up new instances with unsupported and outdated images, we are changing our deprecation process. Going forward, when we deprecate an image, we will be pushing an empty index for the © Info :: LinuxServer.io, 2025
• Back to top LinuxServer.io Status page ⚡
Subscribe via RSS —
diff --git a/issues/2024-10-27-wireguard/index.html b/issues/2024-10-27-wireguard/index.html
index 931f00ec..0de40dad 100644
--- a/issues/2024-10-27-wireguard/index.html
+++ b/issues/2024-10-27-wireguard/index.html
@@ -1,5 +1,5 @@
A little over a year ago we updated our default Wireguard image to no longer support building the Wireguard kernel modules and moved that functionality to the Revisiting the situation now we see that the vast majority of users are now either running a kernel with built-in Wireguard support or a custom kernel, such as on a VPS or NAS, which we have never supported building for. As a result we have decided to deprecate the In practice this means there’s only one case where there will be a still-supported kernel version that doesn’t have built-in Wireguard support: 4.19, which goes EOL at the end of 2025. Our stats show a tiny handful of users that this applies to. If you are still running a 4.19 kernel, or are running any other EOL pre-5.6 kernel, and for whatever reason cannot upgrade then your only option will be to build the Wireguard kernel modules on the host, which the default image (using the We will provide additional reminders of this deprecation towards the end of the year. A little over a year ago we updated our default Wireguard image to no longer support building the Wireguard kernel modules and moved that functionality to the Revisiting the situation now we see that the vast majority of users are now either running a kernel with built-in Wireguard support or a custom kernel, such as on a VPS or NAS, which we have never supported building for. As a result we have decided to deprecate the In practice this means there’s only one case where there will be a still-supported kernel version that doesn’t have built-in Wireguard support: 4.19, which goes EOL at the end of 2025. Our stats show a tiny handful of users that this applies to. If you are still running a 4.19 kernel, or are running any other EOL pre-5.6 kernel, and for whatever reason cannot upgrade then your only option will be to build the Wireguard kernel modules on the host, which the default image (using the We will provide additional reminders of this deprecation towards the end of the year. © Info :: LinuxServer.io, 2025
• Back to top LinuxServer.io Status page ⚡
Subscribe via RSS —
diff --git a/issues/2024-12-24-booksonic-air/index.html b/issues/2024-12-24-booksonic-air/index.html
index 82a530ec..e7d40c00 100644
--- a/issues/2024-12-24-booksonic-air/index.html
+++ b/issues/2024-12-24-booksonic-air/index.html
@@ -1,5 +1,5 @@
Due to a lack of developent by the upstream project, we have decided to deprecate our Booksonic Air container. Due to a lack of developent by the upstream project, we have decided to deprecate our Booksonic Air container. © Info :: LinuxServer.io, 2025
• Back to top LinuxServer.io Status page ⚡
Subscribe via RSS —
diff --git a/issues/2024-12-26-quassel/index.html b/issues/2024-12-26-quassel/index.html
index 99787bce..02bae7e9 100644
--- a/issues/2024-12-26-quassel/index.html
+++ b/issues/2024-12-26-quassel/index.html
@@ -1,6 +1,6 @@
Deprecations
quassel-web
-quassel-core Due to a lack of developent by the upstream projects, we have decided to deprecate our Quassel Core & Quassel Web containers. Due to a lack of developent by the upstream projects, we have decided to deprecate our Quassel Core & Quassel Web containers. © Info :: LinuxServer.io, 2025
• Back to top LinuxServer.io Status page ⚡
Subscribe via RSS —
diff --git a/issues/2025-01-01-wireguard/index.html b/issues/2025-01-01-wireguard/index.html
index 806a1b90..46cb6a0c 100644
--- a/issues/2025-01-01-wireguard/index.html
+++ b/issues/2025-01-01-wireguard/index.html
@@ -1,5 +1,5 @@
A little over a year ago we updated our default Wireguard image to no longer support building the Wireguard kernel modules and moved that functionality to the Revisiting the situation now we see that the vast majority of users are now either running a kernel with built-in Wireguard support or a custom kernel, such as on a VPS or NAS, which we have never supported building for. As previously announced we have now deprecated the In practice this means there’s only one case where there will be a still-supported kernel version that doesn’t have built-in Wireguard support: 4.19, which goes EOL at the end of 2025. Our stats show a tiny handful of users that this applies to. If you are still running a 4.19 kernel, or are running any other EOL pre-5.6 kernel, and for whatever reason cannot upgrade then your only option will be to build the Wireguard kernel modules on the host, which the default image (using the A little over a year ago we updated our default Wireguard image to no longer support building the Wireguard kernel modules and moved that functionality to the Revisiting the situation now we see that the vast majority of users are now either running a kernel with built-in Wireguard support or a custom kernel, such as on a VPS or NAS, which we have never supported building for. As previously announced we have now deprecated the In practice this means there’s only one case where there will be a still-supported kernel version that doesn’t have built-in Wireguard support: 4.19, which goes EOL at the end of 2025. Our stats show a tiny handful of users that this applies to. If you are still running a 4.19 kernel, or are running any other EOL pre-5.6 kernel, and for whatever reason cannot upgrade then your only option will be to build the Wireguard kernel modules on the host, which the default image (using the © Info :: LinuxServer.io, 2025
• Back to top LinuxServer.io Status page ⚡
Subscribe via RSS —
diff --git a/issues/2025-01-18-daapd/index.html b/issues/2025-01-18-daapd/index.html
index 3b280c29..6e84f016 100644
--- a/issues/2025-01-18-daapd/index.html
+++ b/issues/2025-01-18-daapd/index.html
@@ -2,7 +2,7 @@
We recommend switching to their official container."> Due to issues maintaining the necessary level of support and development, we are deprecating our daapd container. We recommend switching to their official container. Due to issues maintaining the necessary level of support and development, we are deprecating our daapd container. We recommend switching to their official container. © Info :: LinuxServer.io, 2025
• Back to top LinuxServer.io Status page ⚡
Subscribe via RSS —
diff --git a/issues/2025-01-30-minetest/index.html b/issues/2025-01-30-minetest/index.html
index 3a417df3..0a8caac9 100644
--- a/issues/2025-01-30-minetest/index.html
+++ b/issues/2025-01-30-minetest/index.html
@@ -1,5 +1,5 @@
Due to the upstream project rebranding, we have decided to deprecate our Minetest image. Please migrate to our new Luanti image instead. © Info :: LinuxServer.io, 2025
• Back to top LinuxServer.io Status page ⚡
Subscribe via RSS —
diff --git a/issues/2025-02-17-fleet/index.html b/issues/2025-02-17-fleet/index.html
index 4e2b2ec3..1a4d6da0 100644
--- a/issues/2025-02-17-fleet/index.html
+++ b/issues/2025-02-17-fleet/index.html
@@ -2,7 +2,7 @@
The new API and images page will serve as a replacement for our Fleet instance."> Due to issues maintaining the necessary level of development, we will be deprecating our Fleet container and Fleet application on June 1st, 2025. The new API and images page will serve as a replacement for our Fleet instance. Due to issues maintaining the necessary level of development, we will be deprecating our Fleet container and Fleet application on June 1st, 2025. The new API and images page will serve as a replacement for our Fleet instance. © Info :: LinuxServer.io, 2025
• Back to top LinuxServer.io Status page ⚡
Subscribe via RSS —
diff --git a/issues/2025-02-19-snapdrop/index.html b/issues/2025-02-19-snapdrop/index.html
index 6ee3c121..be6eaa48 100644
--- a/issues/2025-02-19-snapdrop/index.html
+++ b/issues/2025-02-19-snapdrop/index.html
@@ -1,5 +1,5 @@
Due to the upstream project being purchased by a commercial entity and stopping development, we have decided to deprecate our Snapdrop image. Consider switching to our Pairdrop image for similar functionality. © Info :: LinuxServer.io, 2025
• Back to top LinuxServer.io Status page ⚡
Subscribe via RSS —
diff --git a/issues/2025-04-25-snipe-it/index.html b/issues/2025-04-25-snipe-it/index.html
index 550a208a..ac31c91b 100644
--- a/issues/2025-04-25-snipe-it/index.html
+++ b/issues/2025-04-25-snipe-it/index.html
@@ -1,5 +1,5 @@
Due to challenges in supporting the application, we have decided to deprecate our Snipe-IT image. We recommend migrating to the official docker image from Grokability Due to challenges in supporting the application, we have decided to deprecate our Snipe-IT image. We recommend migrating to the official docker image from Grokability © Info :: LinuxServer.io, 2025
• Back to top LinuxServer.io Status page ⚡
Subscribe via RSS —
diff --git a/issues/2025-05-17-netbootxyz/index.html b/issues/2025-05-17-netbootxyz/index.html
index 245f0aa4..2329c3c7 100644
--- a/issues/2025-05-17-netbootxyz/index.html
+++ b/issues/2025-05-17-netbootxyz/index.html
@@ -1,5 +1,5 @@
We have decided to deprecate our Netboot.xyz image. Consider switching to the official container Netboot.xyz image. The official image can cleanly replace our image. We have decided to deprecate our Netboot.xyz image. Consider switching to the official container Netboot.xyz image. The official image can cleanly replace our image. © Info :: LinuxServer.io, 2025
• Back to top LinuxServer.io Status page ⚡
Subscribe via RSS —
diff --git a/issues/2025-05-24-freetube/index.html b/issues/2025-05-24-freetube/index.html
index 100e06db..185c3080 100644
--- a/issues/2025-05-24-freetube/index.html
+++ b/issues/2025-05-24-freetube/index.html
@@ -1,5 +1,5 @@
We have been made aware that upstream does not approve of this image and have decided to deprecate it. We do not know of any alternatives at this time. We have been made aware that upstream does not approve of this image and have decided to deprecate it. We do not know of any alternatives at this time. © Info :: LinuxServer.io, 2025
• Back to top LinuxServer.io Status page ⚡
Subscribe via RSS —
diff --git a/issues/2025-06-11-emulatorjs/index.html b/issues/2025-06-11-emulatorjs/index.html
index 317bd29b..aa0ec5f5 100644
--- a/issues/2025-06-11-emulatorjs/index.html
+++ b/issues/2025-06-11-emulatorjs/index.html
@@ -14,7 +14,7 @@ https://github.com/webrcade/webrcade">emulatorjs More information here https://www.linuxserver.io/blog/spring-cleaning-new-images-and-rebasing
Please consider using one of these alternatives: https://github.com/gaseous-project/gaseous-server
https://github.com/rommapp/romm/
-https://github.com/webrcade/webrcade © Info :: LinuxServer.io, 2025
• Back to top LinuxServer.io Status page ⚡
Subscribe via RSS —
diff --git a/issues/2025-06-27-readarr/index.html b/issues/2025-06-27-readarr/index.html
index 5bc3b34e..2e6f657e 100644
--- a/issues/2025-06-27-readarr/index.html
+++ b/issues/2025-06-27-readarr/index.html
@@ -1,5 +1,5 @@
Due to upstream retiring the project, due to the lack of developers, we are deprecating the image. Due to upstream retiring the project, due to the lack of developers, we are deprecating the image. © Info :: LinuxServer.io, 2025
• Back to top LinuxServer.io Status page ⚡
Subscribe via RSS —
diff --git a/issues/2025-07-10-sickchill/index.html b/issues/2025-07-10-sickchill/index.html
index b470818e..66809601 100644
--- a/issues/2025-07-10-sickchill/index.html
+++ b/issues/2025-07-10-sickchill/index.html
@@ -1,5 +1,5 @@
Due to a lack of upstream development we have decided to deprecate our Sickchill image. Due to a lack of upstream development we have decided to deprecate our Sickchill image. © Info :: LinuxServer.io, 2025
• Back to top LinuxServer.io Status page ⚡
Subscribe via RSS —
diff --git a/issues/2025-07-27-pylon/index.html b/issues/2025-07-27-pylon/index.html
index 24107cc1..1f85c0d3 100644
--- a/issues/2025-07-27-pylon/index.html
+++ b/issues/2025-07-27-pylon/index.html
@@ -1,5 +1,5 @@
Due to a lack of upstream development we have decided to deprecate our Pylon image. Due to a lack of upstream development we have decided to deprecate our Pylon image. © Info :: LinuxServer.io, 2025
• Back to top LinuxServer.io Status page ⚡
Subscribe via RSS —
diff --git a/issues/2025-08-23-rdesktop/index.html b/issues/2025-08-23-rdesktop/index.html
index 5c496a1a..cf04b808 100644
--- a/issues/2025-08-23-rdesktop/index.html
+++ b/issues/2025-08-23-rdesktop/index.html
@@ -1,5 +1,5 @@
Following the release of our Selkies-based Webtop images, we have decided to begin a phased deprecation of our rdesktop images. Due to substantial overhead in maintaining so many rdesktop-specific images, and with webtop now covering most use cases, this process will start with the removal of all non-Ubuntu image versions on 2025-09-30. If you are currently using a non-Ubuntu version of rdesktop we recommend migrating to one of the Ubuntu tags before this date. Beyond this, we will reassess the usage of the remaining image versions and make a decision as to the viability of the rdesktop platform. Once a decision has been made we will publish information about the process and timescales involved. Following the release of our Selkies-based Webtop images, we have decided to begin a phased deprecation of our rdesktop images. Due to substantial overhead in maintaining so many rdesktop-specific images, and with webtop now covering most use cases, this process will start with the removal of all non-Ubuntu image versions on 2025-09-30. If you are currently using a non-Ubuntu version of rdesktop we recommend migrating to one of the Ubuntu tags before this date. Beyond this, we will reassess the usage of the remaining image versions and make a decision as to the viability of the rdesktop platform. Once a decision has been made we will publish information about the process and timescales involved. © Info :: LinuxServer.io, 2025
• Back to top LinuxServer.io Status page ⚡
Subscribe via RSS —
Changes To Our Image Deprecation Process
August 12, 2024 at 6:00 PMlatest tags (or corresponding branch tags for alternate releases such as develop or nightly). This will make it impossible for someone to pull the latest tag for that image and require them to specifically identify and pull a named version tag. Our hope is that by adding this small hurdle it will dramatically reduce the number of users unknowingly running unsupported images.Changes To Our Image Deprecation Process
August 12, 2024 at 6:00 PMlatest tags (or corresponding branch tags for alternate releases such as develop or nightly). This will make it impossible for someone to pull the latest tag for that image and require them to specifically identify and pull a named version tag. Our hope is that by adding this small hurdle it will dramatically reduce the number of users unknowingly running unsupported images.latest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.Reminder: Wireguard Legacy Tag Deprecation
October 27, 2024 at 8:00 PMlegacy tag. We did this on the basis that most users were running a kernel that already had built-in Wireguard support (5.6 or above in terms of official kernel releases) and this allowed us to reduce the size of the default image by 600Mb for them.legacy tag from the end of 2024.latest tag) will then be able to make use of.legacy tag. We did this on the basis that most users were running a kernel that already had built-in Wireguard support (5.6 or above in terms of official kernel releases) and this allowed us to reduce the size of the default image by 600Mb for them.legacy tag from the end of 2024.latest tag) will then be able to make use of.latest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.Booksonic Air Deprecation Notice
December 24, 2024 at 10:00 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.Quassel Core & Quassel Web Deprecation Notice
December 26, 2024 at 6:00 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.Completed: Wireguard Legacy Tag Deprecation
January 1, 2025 at 12:00 PMlegacy tag. We did this on the basis that most users were running a kernel that already had built-in Wireguard support (5.6 or above in terms of official kernel releases) and this allowed us to reduce the size of the default image by 600Mb for them.legacy tag.latest tag) will then be able to make use of.legacy tag. We did this on the basis that most users were running a kernel that already had built-in Wireguard support (5.6 or above in terms of official kernel releases) and this allowed us to reduce the size of the default image by 600Mb for them.legacy tag.latest tag) will then be able to make use of.latest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.daapd (aka Owntone) Deprecation Notice
January 18, 2025 at 12:00 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.Minetest Deprecation Notice
January 30, 2025 at 10:00 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.Fleet Deprecation Notice
February 17, 2025 at 10:00 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.Snapdrop Deprecation Notice
February 19, 2025 at 10:00 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.Snipe-IT Deprecation Notice
April 25, 2025 at 6:00 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.Netboot.xyz Deprecation Notice
May 17, 2025 at 10:00 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.FreeTube Deprecation Notice
May 24, 2025 at 6:00 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.latest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.Readarr Deprecation Notice
June 27, 2025 at 6:00 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.Sickchill Deprecation Notice
July 10, 2025 at 10:00 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.Pylon Deprecation Notice
July 27, 2025 at 11:00 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.rdesktop Phased Deprecation Notice
August 23, 2025 at 11:00 PMlatest or branch (develop, nightly, etc.) tags and will need to use a specific version tag if you still need access to the image. You can read more about this here.