deploy: 277c2ac

affected/deprecations/index.xml

@@ -1,4 +1,6 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><link rel="alternate" type="text/html" href="https://info.linuxserver.io"/><title>Deprecations on Info :: LinuxServer.io</title><link>https://info.linuxserver.io/affected/deprecations/</link><description>History</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2024-07-16T18:00:00+00:00</lastBuildDate><updated>2024-07-16T18:00:00+00:00</updated><atom:link href="https://info.linuxserver.io/affected/deprecations/index.xml" rel="self" type="application/rss+xml"/><item><title>Wireguard Legacy Tag Deprecation</title><link>https://info.linuxserver.io/issues/2024-07-16-wireguard/</link><pubDate>Tue, 16 Jul 2024 18:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2024-07-16-wireguard/</guid><category/><description>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 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.</description><content type="html">&lt;p>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 &lt;code>legacy&lt;/code> 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.&lt;/p>
+<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><link rel="alternate" type="text/html" href="https://info.linuxserver.io"/><title>Deprecations on Info :: LinuxServer.io</title><link>https://info.linuxserver.io/affected/deprecations/</link><description>History</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2024-08-12T18:00:00+00:00</lastBuildDate><updated>2024-08-12T18:00:00+00:00</updated><atom:link href="https://info.linuxserver.io/affected/deprecations/index.xml" rel="self" type="application/rss+xml"/><item><title>Changes To Our Image Deprecation Process</title><link>https://info.linuxserver.io/issues/2024-08-11-deprecation-changes/</link><pubDate>Mon, 12 Aug 2024 18:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2024-08-11-deprecation-changes/</guid><category/><description>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&amp;rsquo;t read the notices, or use a container management platform that doesn&amp;rsquo;t expose them.</description><content type="html">&lt;p>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&amp;rsquo;t read the notices, or use a container management platform that doesn&amp;rsquo;t expose them.&lt;/p>
+&lt;p>Wherever possible we want to avoid actually removing images from registries, because it can prevent legitimate uses of them &amp;amp; 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.&lt;/p>
+&lt;p>Going forward, when we deprecate an image, we will be pushing an empty index for the &lt;code>latest&lt;/code> tags (or corresponding branch tags for alternate releases such as develop or nightly). This will make it impossible for someone to pull the &lt;code>latest&lt;/code> 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.&lt;/p></content></item><item><title>Wireguard Legacy Tag Deprecation</title><link>https://info.linuxserver.io/issues/2024-07-16-wireguard/</link><pubDate>Tue, 16 Jul 2024 18:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2024-07-16-wireguard/</guid><category/><description>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 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.</description><content type="html">&lt;p>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 &lt;code>legacy&lt;/code> 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.&lt;/p>
 &lt;p>Revisiting the situation now we see that the vast majority of users are now either running a kernel with built-in Wireguard support &lt;em>or&lt;/em> 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 &lt;code>legacy&lt;/code> tag from the end of 2024.&lt;/p>
 &lt;p>In practice this means there&amp;rsquo;s only one case where there will be a still-supported kernel version that doesn&amp;rsquo;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.&lt;/p>
 &lt;p>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 &lt;em>on the host&lt;/em>, which the default image (using the &lt;code>latest&lt;/code> tag) will then be able to make use of.&lt;/p>

index.html

@@ -14,7 +14,8 @@
 <b>Security</b>
 <span class=category-status></span></div><div class=components><div class=component data-status=ok><a href=/affected/vulnerabilities/ class=no-underline>Vulnerabilities</a>
 <span class=component-status>OK</span></div></div><script>thisCategory=document.currentScript.parentNode,componentsOfThisCategory=thisCategory.querySelectorAll('.component');var highestLevelStatus='',highestLevelStatusReadable;function checkStatus(t){var e=t.getAttribute('data-status');e==='down'?highestLevelStatus='down':e==='disrupted'&&highestLevelStatus!=='down'?highestLevelStatus='disrupted':e==='notice'&&highestLevelStatus!=='down'&&highestLevelStatus!=='disrupted'&&(highestLevelStatus='notice')}componentsOfThisCategory.forEach(e=>checkStatus(e)),highestLevelStatusReadable=highestLevelStatus,highestLevelStatus==='ok'&&(highestLevelStatusReadable='OK'),highestLevelStatus==='notice'&&(highestLevelStatusReadable='Notice'),highestLevelStatus==='disrupted'&&(highestLevelStatusReadable='Disrupted'),highestLevelStatus==='down'&&(highestLevelStatusReadable='Down'),thisCategory.classList.contains('category--titled')&&(thisCategory.querySelector('.category__head').setAttribute('data-status',highestLevelStatus),thisCategory.querySelector('.category-status').innerHTML=highestLevelStatusReadable)</script></div></div></div><div class="contain contain--more"><h2 class=center>History</h2><hr class=clean></div><div class="contain contain--more" id=incidents><p class="center archive__head" id=archive-2024><a href=#archive-2024 class=no-underline><strong>2024</strong>
-<span class=faded>(20)</span></a></p><a href=https://info.linuxserver.io/issues/2024-07-26-rust-ungoogled/ class="issue no-underline"><small class="date float-right relative-time" title="July 26, 2024 at 8:00 PM" data-date="Jul 26 20:00:00 2024 UTC">July 26, 2024 at 8:00 PM</small><h3>New Containers: RustDesk and Ungoogled Chromium &nbsp;ℹ</h3><span class=faded>We have released two new desktop application containers for: RustDesk
+<span class=faded>(21)</span></a></p><a href=https://info.linuxserver.io/issues/2024-08-11-deprecation-changes/ class="issue no-underline"><small class="date float-right relative-time" title="August 12, 2024 at 6:00 PM" data-date="Aug 12 18:00:00 2024 UTC">August 12, 2024 at 6:00 PM</small><h3>Changes To Our Image Deprecation Process &nbsp;ℹ</h3><span class=faded>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. …</span></a>
+<a href=https://info.linuxserver.io/issues/2024-07-26-rust-ungoogled/ class="issue no-underline"><small class="date float-right relative-time" title="July 26, 2024 at 8:00 PM" data-date="Jul 26 20:00:00 2024 UTC">July 26, 2024 at 8:00 PM</small><h3>New Containers: RustDesk and Ungoogled Chromium &nbsp;ℹ</h3><span class=faded>We have released two new desktop application containers for: RustDesk
 RustDesk is a full-featured open source remote control alternative for self-hosting and security with minimal configuration. …</span></a>
 <a href=https://info.linuxserver.io/issues/2024-07-24-manyfold/ class="issue no-underline"><small class="date float-right relative-time" title="July 24, 2024 at 12:00 PM" data-date="Jul 24 12:00:00 2024 UTC">July 24, 2024 at 12:00 PM</small><h3>New Container: Manyfold &nbsp;ℹ</h3><span class=faded>We have released a new container for Manyfold!
 Manyfold is an open source, self-hosted web application for managing a collection of 3D models, particularly focused on 3D printing.</span></a>

index.json

@@ -1 +1 @@
-{"is":"index","cStateVersion":"5.6.1","apiVersion":"2.0","title":"Info :: LinuxServer.io","languageCodeHTML":"en","languageCode":"en","baseURL":"https://info.linuxserver.io","description":"LinuxServer.io Status page","summaryStatus":"ok","categories":[{"name":"Images","description":"Information regarding our images","hideTitle":false,"closedByDefault":false},{"name":"Security","hideTitle":false,"closedByDefault":false}],"pinnedIssues":[],"systems":[{"name":"Deprecations","category":"Images","status":"ok","unresolvedIssues":[]},{"name":"New Containers","category":"Images","status":"ok","unresolvedIssues":[]},{"name":"Vulnerabilities","category":"Security","status":"ok","unresolvedIssues":[]},{"name":"Known Issues","category":"Images","status":"ok","unresolvedIssues":[]},{"name":"Notifications","category":"Images","status":"ok","unresolvedIssues":[]}],"buildDate":"2024-07-25","buildTime":"23:52","buildTimezone":"UTC","colorBrand":"#0a0c0f","colorOk":"#008000","colorDisrupted":"#cc4400","colorDown":"#e60000","colorNotice":"#24478f","alwaysKeepBrandColor":"true","logo":"https://info.linuxserver.io/logo.png","googleAnalytics":"UA-00000000-1"}
+{"is":"index","cStateVersion":"5.6.1","apiVersion":"2.0","title":"Info :: LinuxServer.io","languageCodeHTML":"en","languageCode":"en","baseURL":"https://info.linuxserver.io","description":"LinuxServer.io Status page","summaryStatus":"ok","categories":[{"name":"Images","description":"Information regarding our images","hideTitle":false,"closedByDefault":false},{"name":"Security","hideTitle":false,"closedByDefault":false}],"pinnedIssues":[],"systems":[{"name":"Deprecations","category":"Images","status":"ok","unresolvedIssues":[]},{"name":"New Containers","category":"Images","status":"ok","unresolvedIssues":[]},{"name":"Vulnerabilities","category":"Security","status":"ok","unresolvedIssues":[]},{"name":"Known Issues","category":"Images","status":"ok","unresolvedIssues":[]},{"name":"Notifications","category":"Images","status":"ok","unresolvedIssues":[]}],"buildDate":"2024-08-11","buildTime":"17:25","buildTimezone":"UTC","colorBrand":"#0a0c0f","colorOk":"#008000","colorDisrupted":"#cc4400","colorDown":"#e60000","colorNotice":"#24478f","alwaysKeepBrandColor":"true","logo":"https://info.linuxserver.io/logo.png","googleAnalytics":"UA-00000000-1"}

index.xml

@@ -1,4 +1,6 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Info :: LinuxServer.io</title><link>https://info.linuxserver.io/</link><description>History</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>Fri, 26 Jul 2024 20:00:00 +0000</lastBuildDate><atom:link href="https://info.linuxserver.io/index.xml" rel="self" type="application/rss+xml"/><item><title>New Containers: RustDesk and Ungoogled Chromium</title><link>https://info.linuxserver.io/issues/2024-07-26-rust-ungoogled/</link><pubDate>Fri, 26 Jul 2024 20:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2024-07-26-rust-ungoogled/</guid><category/><description>&lt;p>We have released two new desktop application containers for:
+<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Info :: LinuxServer.io</title><link>https://info.linuxserver.io/</link><description>History</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>Mon, 12 Aug 2024 18:00:00 +0000</lastBuildDate><atom:link href="https://info.linuxserver.io/index.xml" rel="self" type="application/rss+xml"/><item><title>Changes To Our Image Deprecation Process</title><link>https://info.linuxserver.io/issues/2024-08-11-deprecation-changes/</link><pubDate>Mon, 12 Aug 2024 18:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2024-08-11-deprecation-changes/</guid><category/><description>&lt;p>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&amp;rsquo;t read the notices, or use a container management platform that doesn&amp;rsquo;t expose them.&lt;/p>
+&lt;p>Wherever possible we want to avoid actually removing images from registries, because it can prevent legitimate uses of them &amp;amp; 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.&lt;/p>
+&lt;p>Going forward, when we deprecate an image, we will be pushing an empty index for the &lt;code>latest&lt;/code> tags (or corresponding branch tags for alternate releases such as develop or nightly). This will make it impossible for someone to pull the &lt;code>latest&lt;/code> 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.&lt;/p></description></item><item><title>New Containers: RustDesk and Ungoogled Chromium</title><link>https://info.linuxserver.io/issues/2024-07-26-rust-ungoogled/</link><pubDate>Fri, 26 Jul 2024 20:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2024-07-26-rust-ungoogled/</guid><category/><description>&lt;p>We have released two new desktop application containers for:
 &lt;a href="https://github.com/linuxserver/docker-rustdesk">RustDesk&lt;/a>&lt;/p>
 &lt;p>&lt;a href="https://rustdesk.com/">RustDesk&lt;/a> is a full-featured open source remote control alternative for self-hosting and security with minimal configuration.&lt;/p>
 &lt;p>&lt;a href="https://github.com/linuxserver/docker-ungoogled-chromium">Ungoogled Chromium&lt;/a>&lt;/p>