mirror of
https://github.com/linuxserver/cstate.git
synced 2026-01-20 20:12:05 +08:00
280 lines
26 KiB
XML
280 lines
26 KiB
XML
<?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>diskover on Info :: LinuxServer.io</title><link>https://info.linuxserver.io/affected/diskover/</link><description>History</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2023-11-02T23:00:00+00:00</lastBuildDate><updated>2023-11-02T23:00:00+00:00</updated><atom:link href="https://info.linuxserver.io/affected/diskover/index.xml" rel="self" type="application/rss+xml"/><item><title>Notification: Significant changes to cron</title><link>https://info.linuxserver.io/issues/2023-11-02-cron/</link><pubDate>Thu, 02 Nov 2023 23:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2023-11-02-cron/</guid><category/><description>We&rsquo;ve decided to make some changes to how cron is shipped in our images.
|
|
Previous state of cron We have not had a consistent standard. Many of our images do however setup cron the same way. When an application requires cron, we setup crontabs for abc or root in /config/crontabs/. This has allowed users to customize crontabs.
|
|
This has required that if we make changes to the image that require changes to crontabs we have had to carefully plan how to make adjustments to existing user files without causing issues with any customizations.</description><content type="html"><p>We&rsquo;ve decided to make some changes to how cron is shipped in our images.</p>
|
|
<h2 id="previous-state-of-cron">Previous state of cron</h2>
|
|
<p>We have not had a consistent standard. Many of our images do however setup cron the same way. When an application requires cron, we setup crontabs for <code>abc</code> or <code>root</code> in <code>/config/crontabs/</code>. This has allowed users to customize crontabs.</p>
|
|
<p>This has required that if we make changes to the image that require changes to crontabs we have had to carefully plan how to make adjustments to existing user files without causing issues with any customizations. It could also mean we are unable to automatically make required changes if user customizations make an automated adjustments impossible. In these cases, users have been required to update crontabs on their own.</p>
|
|
<p>As a side note, we also offer our <a href="https://github.com/linuxserver/docker-mods/tree/universal-cron">universal cron mod</a> that can be applied to add the ability to use cron for both <code>abc</code> and <code>root</code> in any container.</p>
|
|
<h2 id="going-forward">Going forward</h2>
|
|
<p>When an application requires cron, we will also no longer setup crontabs for <code>abc</code> or <code>root</code> in <code>/config/crontabs/</code>, unless user customizations to the crontab are required.</p>
|
|
<p>Instead, we are internalizing the crontab files. This should make it easier for us to update crontabs when changes to the image require updates to crontabs. It also means users won&rsquo;t have to keep up with changes to crontab requirements that may break their applications.</p>
|
|
<p><strong>IMPORTANT:</strong> We are NOT removing existing crontabs from <code>/config/crontabs/</code>, they will simply be ignored unless otherwise noted.</p>
|
|
<p>We will continue to offer our <a href="https://github.com/linuxserver/docker-mods/tree/universal-cron">universal cron mod</a> with a new purpose of making crontabs for <code>abc</code> and <code>root</code> customizable by setting them up in up <code>/config/crontabs/</code> and configuring the cron service to recognize them, essentially restoring the original behavior. This effectively makes the cron mod the only way to customize crontabs.</p>
|
|
<p>As a side note, we are also adjusting all existing crontabs we ship to run as <code>abc</code> instead of <code>root</code>. This improves security and consistency in our images.</p>
|
|
<h3 id="exceptions">Exceptions</h3>
|
|
<p>Diskover requires setting your own crontab schedule. The container will now run cron using <code>/config/crontabs/abc</code> instead of <code>/config/crontabs/root</code>. The <code>/config/crontabs/root</code> file is NOT being automatically removed, but will be ignored.</p>
|
|
<p>Rsnapshot requires setting your own crontab schedule, and in some cases requires backups to run as root. The container will continue to run cron using <code>/config/crontabs/root</code>.</p>
|
|
<h2 id="timing">Timing</h2>
|
|
<p>You can expect to see these changes merge today, and begin building into our images over the next few days and weeks.</p></content></item><item><title>Notification: Significant changes to cron incoming</title><link>https://info.linuxserver.io/issues/2023-10-20-cron/</link><pubDate>Fri, 20 Oct 2023 23:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2023-10-20-cron/</guid><category/><description>We&rsquo;ve decided to make some changes to how cron is shipped in our images.
|
|
Current state of cron We have not had a consistent standard. Many of our images do however setup cron the same way. When an application requires cron, we setup crontabs for abc or root in /config/crontabs/. This has allowed users to customize crontabs.
|
|
This has required that if we make changes to the image that require changes to crontabs we have had to carefully plan how to make adjustments to existing user files without causing issues with any customizations.</description><content type="html"><p>We&rsquo;ve decided to make some changes to how cron is shipped in our images.</p>
|
|
<h2 id="current-state-of-cron">Current state of cron</h2>
|
|
<p>We have not had a consistent standard. Many of our images do however setup cron the same way. When an application requires cron, we setup crontabs for <code>abc</code> or <code>root</code> in <code>/config/crontabs/</code>. This has allowed users to customize crontabs.</p>
|
|
<p>This has required that if we make changes to the image that require changes to crontabs we have had to carefully plan how to make adjustments to existing user files without causing issues with any customizations. It could also mean we are unable to automatically make required changes if user customizations make an automated adjustments impossible. In these cases, users have been required to update crontabs on their own.</p>
|
|
<p>As a side note, we also offer our <a href="https://github.com/linuxserver/docker-mods/tree/universal-cron">universal cron mod</a> that can be applied to add the ability to use cron for both <code>abc</code> and <code>root</code> in any container.</p>
|
|
<h2 id="incoming-changes">Incoming changes</h2>
|
|
<p>When an application requires cron, we will also no longer setup crontabs for <code>abc</code> or <code>root</code> in <code>/config/crontabs/</code>, unless user customizations to the crontab are required.</p>
|
|
<p>Instead, we are internalizing the crontab files. This should make it easier for us to update crontabs when changes to the image require updates to crontabs. It also means users won&rsquo;t have to keep up with changes to crontab requirements that may break their applications.</p>
|
|
<p><strong>IMPORTANT:</strong> We are NOT removing existing crontabs from <code>/config/crontabs/</code>, they will simply be ignored unless otherwise noted.</p>
|
|
<p>We will continue to offer our <a href="https://github.com/linuxserver/docker-mods/tree/universal-cron">universal cron mod</a> with a new purpose of making crontabs for <code>abc</code> and <code>root</code> customizable by setting them up in up <code>/config/crontabs/</code> and configuring the cron service to recognize them, essentially restoring the original behavior. This effectively makes the cron mod the only way to customize crontabs.</p>
|
|
<p>As a side note, we are also adjusting all existing crontabs we ship to run as <code>abc</code> instead of <code>root</code>. This improves security and consistency in our images.</p>
|
|
<h3 id="exceptions">Exceptions</h3>
|
|
<p>Diskover requires setting your own crontab schedule. The container will now run cron using <code>/config/crontabs/abc</code> instead of <code>/config/crontabs/root</code>. The <code>/config/crontabs/root</code> file is NOT being automatically removed, but will be ignored.</p>
|
|
<p>Rsnapshot requires setting your own crontab schedule, and in some cases requires backups to run as root. The container will continue to run cron using <code>/config/crontabs/root</code>.</p>
|
|
<h2 id="timing">Timing</h2>
|
|
<p>You can expect to see these changes merge around November 1st, 2023. An additional post will be made with all of the above information and any updates if anything changes between now and then.</p></content></item><item><title>Notification: Significant changes to cron incoming</title><link>https://info.linuxserver.io/issues/2023-10-01-cron/</link><pubDate>Sun, 01 Oct 2023 23:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2023-10-01-cron/</guid><category/><description>We&rsquo;ve decided to make some changes to how cron is shipped in our images.
|
|
Current state of cron We have not had a consistent standard. Many of our images do however setup cron the same way. When an application requires cron, we setup crontabs for abc or root in /config/crontabs/. This has allowed users to customize crontabs.
|
|
This has required that if we make changes to the image that require changes to crontabs we have had to carefully plan how to make adjustments to existing user files without causing issues with any customizations.</description><content type="html"><p>We&rsquo;ve decided to make some changes to how cron is shipped in our images.</p>
|
|
<h2 id="current-state-of-cron">Current state of cron</h2>
|
|
<p>We have not had a consistent standard. Many of our images do however setup cron the same way. When an application requires cron, we setup crontabs for <code>abc</code> or <code>root</code> in <code>/config/crontabs/</code>. This has allowed users to customize crontabs.</p>
|
|
<p>This has required that if we make changes to the image that require changes to crontabs we have had to carefully plan how to make adjustments to existing user files without causing issues with any customizations. It could also mean we are unable to automatically make required changes if user customizations make an automated adjustments impossible. In these cases, users have been required to update crontabs on their own.</p>
|
|
<p>As a side note, we also offer our <a href="https://github.com/linuxserver/docker-mods/tree/universal-cron">universal cron mod</a> that can be applied to add the ability to use cron for both <code>abc</code> and <code>root</code> in any container.</p>
|
|
<h2 id="incoming-changes">Incoming changes</h2>
|
|
<p>When an application requires cron, we will also no longer setup crontabs for <code>abc</code> or <code>root</code> in <code>/config/crontabs/</code>, unless user customizations to the crontab are required.</p>
|
|
<p>Instead, we are internalizing the crontab files. This should make it easier for us to update crontabs when changes to the image require updates to crontabs. It also means users won&rsquo;t have to keep up with changes to crontab requirements that may break their applications.</p>
|
|
<p><strong>IMPORTANT:</strong> We are NOT removing existing crontabs from <code>/config/crontabs/</code>, they will simply be ignored unless otherwise noted.</p>
|
|
<p>We will continue to offer our <a href="https://github.com/linuxserver/docker-mods/tree/universal-cron">universal cron mod</a> with a new purpose of making crontabs for <code>abc</code> and <code>root</code> customizable by setting them up in up <code>/config/crontabs/</code> and configuring the cron service to recognize them, essentially restoring the original behavior. This effectively makes the cron mod the only way to customize crontabs.</p>
|
|
<p>As a side note, we are also adjusting all existing crontabs we ship to run as <code>abc</code> instead of <code>root</code>. This improves security and consistency in our images.</p>
|
|
<h3 id="exceptions">Exceptions</h3>
|
|
<p>Diskover requires setting your own crontab schedule. The container will now run cron using <code>/config/crontabs/abc</code> instead of <code>/config/crontabs/root</code>. The <code>/config/crontabs/root</code> file is NOT being automatically removed, but will be ignored.</p>
|
|
<p>Rsnapshot requires setting your own crontab schedule, and in some cases requires backups to run as root. The container will continue to run cron using <code>/config/crontabs/root</code>.</p>
|
|
<h2 id="timing">Timing</h2>
|
|
<p>You can expect to see these changes merge around November 1st, 2023. An additional post will be made with all of the above information and any updates if anything changes between now and then.</p></content></item><item><title>Notification: Significant changes to nginx based images</title><link>https://info.linuxserver.io/issues/2022-08-20-nginx-base/</link><pubDate>Sat, 20 Aug 2022 18:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2022-08-20-nginx-base/</guid><category/><description>Most images using our alpine-nginx base image are being updated to alpine 3.15 with php8 and some significant changes to the nginx configs.
|
|
Changes you will likely notice:
|
|
Bring our default shipped configs as close as possible to alpine upstream defaults https://git.alpinelinux.org/aports/tree/main/nginx/nginx.conf?h=3.15-stable Include worker_processes.conf and init script to generate it in the base Include resolver.conf and init script to generate it in the base Include ssl.conf in the base (the same as what is currently shipped in SWAG, but adjusted to use the self-signed certs generated by the base) include /config/nginx/site-confs/*.</description><content type="html"><p>Most images using our alpine-nginx base image are being updated to alpine 3.15 with php8 and some significant changes to the nginx configs.</p>
|
|
<p>Changes you will likely notice:</p>
|
|
<ul>
|
|
<li>Bring our default shipped configs as close as possible to alpine upstream defaults
|
|
<ul>
|
|
<li><a href="https://git.alpinelinux.org/aports/tree/main/nginx/nginx.conf?h=3.15-stable">https://git.alpinelinux.org/aports/tree/main/nginx/nginx.conf?h=3.15-stable</a></li>
|
|
</ul>
|
|
</li>
|
|
<li>Include <code>worker_processes.conf</code> and init script to generate it in the base</li>
|
|
<li>Include <code>resolver.conf</code> and init script to generate it in the base</li>
|
|
<li>Include <code>ssl.conf</code> in the base (the same as what is currently shipped in SWAG, but adjusted to use the self-signed certs generated by the base)</li>
|
|
<li><code>include /config/nginx/site-confs/*.conf;</code> with <code>*.conf</code> extension (rename existing user files automatically)</li>
|
|
<li>Rework <code>default.conf</code>
|
|
<ul>
|
|
<li>Expect applications inside containers to exist at <code>/app/www/public/</code>, and if that does not exist, use <code>/config/www</code></li>
|
|
<li>Include ipv6 support</li>
|
|
<li>deny access to <code>.htaccess</code>/<code>.htpasswd</code> files</li>
|
|
<li>adjust php location and <code>fastcgi_params</code> to use <code>PATH_INFO</code> and mitigate <code>HTTP_PROXY</code> vulnerability</li>
|
|
</ul>
|
|
</li>
|
|
<li>Restructure nginx configs
|
|
<ul>
|
|
<li>Configs in <code>/defaults/nginx/</code> are recursively copied to the user&rsquo;s <code>/config/nginx/</code> (maintaining the structure)</li>
|
|
<li>All configs are now named <code>*.sample</code> and all include <code>## Version YYYY/MM/DD - Changelog: &lt;url to repo history&gt;</code> used by <code>/etc/cont-init.d/85-version-checks</code>
|
|
<ul>
|
|
<li>Required configs (<code>/config/nginx/nginx.conf</code>, <code>/config/nginx/server-confs/ssl.conf</code> and <code>/config/nginx/site-confs/default.conf</code>) are enabled by default. Downstream images can include and/or enable others as needed (ex: SWAG will enable <code>/config/nginx/location-confs/proxy.conf</code> and <code>/config/nginx/server-confs/502.conf</code>)</li>
|
|
</ul>
|
|
</li>
|
|
<li>Folder structure is as follows (in the <code>/config/nginx/</code> context):
|
|
<ul>
|
|
<li>All nginx based images:
|
|
<ul>
|
|
<li>Includes <code>nginx.conf</code> (enabled by default)</li>
|
|
<li>Includes <code>resolver.conf</code> (enabled by default)</li>
|
|
<li>Includes <code>ssl.conf</code> (enabled by default)</li>
|
|
<li>Includes <code>worker_processes.conf</code> (enabled by default)</li>
|
|
<li><code>/config/nginx/site-confs/*</code> included inside the <code>http</code> context in <code>/config/nginx/nginx.conf</code>
|
|
<ul>
|
|
<li>Includes <code>default.conf</code> (enabled by default)</li>
|
|
</ul>
|
|
</li>
|
|
</ul>
|
|
</li>
|
|
<li>SWAG:
|
|
<ul>
|
|
<li>Includes <code>502.conf</code> (enabled by default)</li>
|
|
<li>Includes <code>authelia-location.conf</code></li>
|
|
<li>Includes <code>authelia-server.conf</code></li>
|
|
<li>Includes <code>ldap-location.conf</code></li>
|
|
<li>Includes <code>ldap-server.conf</code></li>
|
|
<li>Includes <code>proxy.conf</code> (enabled by default)</li>
|
|
</ul>
|
|
</li>
|
|
</ul>
|
|
</li>
|
|
</ul>
|
|
</li>
|
|
</ul>
|
|
<p>Under the hood:</p>
|
|
<ul>
|
|
<li>Split out init scripts
|
|
<ul>
|
|
<li><code>root/migrations/01-nginx-site-confs-default</code> migrate existing <code>default</code> to <code>default.conf</code></li>
|
|
<li><code>root/etc/cont-init.d/11-folders</code> creates all the folders needed in <code>/config</code></li>
|
|
<li><code>root/etc/cont-init.d/12-samples</code> removes existing <code>*.sample</code> files from <code>/config/nginx</code> and copies any included <code>*.sample</code> files from the image</li>
|
|
<li><code>root/etc/cont-init.d/13-nginx</code> enable required configs (<code>nginx.conf</code>, <code>ssl.conf</code> and <code>default.conf</code>) if they don&rsquo;t exist, setup <code>dhparams.pem</code>, setup <code>resolver.conf</code>, setup <code>worker_processes.conf</code></li>
|
|
<li><code>root/etc/cont-init.d/14-php</code> configure php</li>
|
|
<li><code>root/etc/cont-init.d/15-keygen</code> create self signed certificates for <code>ssl.conf</code></li>
|
|
<li><code>root/etc/cont-init.d/20-permissions</code> set <code>/config</code> permissions</li>
|
|
<li><code>root/etc/cont-init.d/85-version-checks</code> check all enabled <code>*.conf</code> files against all <code>*.sample</code> files shipped with the image and alert the user about updates</li>
|
|
</ul>
|
|
</li>
|
|
</ul>
|
|
<p>Status of affected images:</p>
|
|
<table>
|
|
<thead>
|
|
<tr>
|
|
<th>Image</th>
|
|
<th>Branch</th>
|
|
<th>PR</th>
|
|
<th>Notes</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody>
|
|
<tr>
|
|
<td>baseimage-alpine-nginx</td>
|
|
<td>master</td>
|
|
<td><a href="https://github.com/linuxserver/docker-baseimage-alpine-nginx/pull/84">https://github.com/linuxserver/docker-baseimage-alpine-nginx/pull/84</a></td>
|
|
<td></td>
|
|
</tr>
|
|
<tr>
|
|
<td>bookstack</td>
|
|
<td>master</td>
|
|
<td><a href="https://github.com/linuxserver/docker-bookstack/pull/113">https://github.com/linuxserver/docker-bookstack/pull/113</a></td>
|
|
<td></td>
|
|
</tr>
|
|
<tr>
|
|
<td>cops</td>
|
|
<td>master</td>
|
|
<td><a href="https://github.com/linuxserver/docker-cops/pull/34">https://github.com/linuxserver/docker-cops/pull/34</a></td>
|
|
<td>composer downgraded to v1 for compatibility</td>
|
|
</tr>
|
|
<tr>
|
|
<td>diskover</td>
|
|
<td>master</td>
|
|
<td><a href="https://github.com/linuxserver/docker-diskover/pull/43">https://github.com/linuxserver/docker-diskover/pull/43</a></td>
|
|
<td></td>
|
|
</tr>
|
|
<tr>
|
|
<td>dokuwiki</td>
|
|
<td>master</td>
|
|
<td><a href="https://github.com/linuxserver/docker-dokuwiki/pull/43">https://github.com/linuxserver/docker-dokuwiki/pull/43</a></td>
|
|
<td></td>
|
|
</tr>
|
|
<tr>
|
|
<td>freshrss</td>
|
|
<td>master</td>
|
|
<td><a href="https://github.com/linuxserver/docker-freshrss/pull/40">https://github.com/linuxserver/docker-freshrss/pull/40</a></td>
|
|
<td></td>
|
|
</tr>
|
|
<tr>
|
|
<td>grav</td>
|
|
<td>main</td>
|
|
<td><a href="https://github.com/linuxserver/docker-grav/pull/9">https://github.com/linuxserver/docker-grav/pull/9</a></td>
|
|
<td></td>
|
|
</tr>
|
|
<tr>
|
|
<td>grocy</td>
|
|
<td>master</td>
|
|
<td><a href="https://github.com/linuxserver/docker-grocy/pull/52">https://github.com/linuxserver/docker-grocy/pull/52</a></td>
|
|
<td></td>
|
|
</tr>
|
|
<tr>
|
|
<td>heimdall</td>
|
|
<td>main</td>
|
|
<td><a href="https://github.com/linuxserver/docker-heimdall/pull/79">https://github.com/linuxserver/docker-heimdall/pull/79</a></td>
|
|
<td></td>
|
|
</tr>
|
|
<tr>
|
|
<td>librespeed</td>
|
|
<td>master</td>
|
|
<td><a href="https://github.com/linuxserver/docker-librespeed/pull/15">https://github.com/linuxserver/docker-librespeed/pull/15</a></td>
|
|
<td></td>
|
|
</tr>
|
|
<tr>
|
|
<td>lychee</td>
|
|
<td>master</td>
|
|
<td><a href="https://github.com/linuxserver/docker-lychee/pull/51">https://github.com/linuxserver/docker-lychee/pull/51</a></td>
|
|
<td></td>
|
|
</tr>
|
|
<tr>
|
|
<td>muximux</td>
|
|
<td>master</td>
|
|
<td><a href="https://github.com/linuxserver/docker-muximux/pull/26">https://github.com/linuxserver/docker-muximux/pull/26</a></td>
|
|
<td></td>
|
|
</tr>
|
|
<tr>
|
|
<td>nextcloud</td>
|
|
<td>master</td>
|
|
<td><a href="https://github.com/linuxserver/docker-nextcloud/pull/219">https://github.com/linuxserver/docker-nextcloud/pull/219</a></td>
|
|
<td></td>
|
|
</tr>
|
|
<tr>
|
|
<td>nginx</td>
|
|
<td>master</td>
|
|
<td><a href="https://github.com/linuxserver/docker-nginx/pull/79">https://github.com/linuxserver/docker-nginx/pull/79</a></td>
|
|
<td></td>
|
|
</tr>
|
|
<tr>
|
|
<td>photoshow</td>
|
|
<td>master</td>
|
|
<td><a href="https://github.com/linuxserver/docker-photoshow/pull/28">https://github.com/linuxserver/docker-photoshow/pull/28</a></td>
|
|
<td><a href="https://info.linuxserver.io/issues/2022-10-14-photoshow/">Deprecated</a></td>
|
|
</tr>
|
|
<tr>
|
|
<td>phpmyadmin</td>
|
|
<td>main</td>
|
|
<td><a href="https://github.com/linuxserver/docker-phpmyadmin/pull/12">https://github.com/linuxserver/docker-phpmyadmin/pull/12</a></td>
|
|
<td></td>
|
|
</tr>
|
|
<tr>
|
|
<td>piwigo</td>
|
|
<td>master</td>
|
|
<td><a href="https://github.com/linuxserver/docker-piwigo/pull/49">https://github.com/linuxserver/docker-piwigo/pull/49</a></td>
|
|
<td></td>
|
|
</tr>
|
|
<tr>
|
|
<td>pixapop</td>
|
|
<td>master</td>
|
|
<td><a href="https://github.com/linuxserver/docker-pixapop/pull/11">https://github.com/linuxserver/docker-pixapop/pull/11</a></td>
|
|
<td><a href="https://info.linuxserver.io/issues/2022-10-14-pixapop">Deprecated</a></td>
|
|
</tr>
|
|
<tr>
|
|
<td>projectsend</td>
|
|
<td>master</td>
|
|
<td><a href="https://github.com/linuxserver/docker-projectsend/pull/22">https://github.com/linuxserver/docker-projectsend/pull/22</a></td>
|
|
<td></td>
|
|
</tr>
|
|
<tr>
|
|
<td>snapdrop</td>
|
|
<td>master</td>
|
|
<td><a href="https://github.com/linuxserver/docker-snapdrop/pull/6">https://github.com/linuxserver/docker-snapdrop/pull/6</a></td>
|
|
<td></td>
|
|
</tr>
|
|
<tr>
|
|
<td>snipe-it</td>
|
|
<td>master</td>
|
|
<td><a href="https://github.com/linuxserver/docker-snipe-it/pull/28">https://github.com/linuxserver/docker-snipe-it/pull/28</a></td>
|
|
<td></td>
|
|
</tr>
|
|
<tr>
|
|
<td>swag</td>
|
|
<td>master</td>
|
|
<td><a href="https://github.com/linuxserver/docker-swag/pull/169">https://github.com/linuxserver/docker-swag/pull/169</a></td>
|
|
<td></td>
|
|
</tr>
|
|
<tr>
|
|
<td>xbackbone</td>
|
|
<td>main</td>
|
|
<td><a href="https://github.com/linuxserver/docker-xbackbone/pull/5">https://github.com/linuxserver/docker-xbackbone/pull/5</a></td>
|
|
<td></td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
<p>Any images with notes above may not be merged. We will make efforts to update this page if any of the images with notes above are merged at a later date. We may also make individual announcements about status updates regarding these images.</p></content></item><item><title>New Container: Diskover</title><link>https://info.linuxserver.io/issues/2018-11-01-diskover/</link><pubDate>Thu, 01 Nov 2018 00:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2018-11-01-diskover/</guid><category/><description>We have released a new container for Diskover!
|
|
diskover is a file system crawler and disk space usage software that uses Elasticsearch to index and manage data across heterogeneous storage systems.</description><content type="html"><p>We have released a new container for <a href="https://github.com/linuxserver/docker-diskover">Diskover</a>!</p>
|
|
<p><a href="https://github.com/shirosaidev/diskover">diskover</a> is a file system crawler and disk space usage software that uses Elasticsearch to index and manage data across heterogeneous storage systems.</p></content></item></channel></rss> |