mirror of
https://github.com/linuxserver/cstate.git
synced 2026-02-20 07:55:25 +08:00
deploy: ee0de091329386b5d6b6b4c9184b84db5934f3ab
This commit is contained in:
nemchik
parent
1d8ae328ac
commit
7a9d69ff06
File diff suppressed because one or more lines are too long
@ -1 +1 @@
|
||||
{"is":"system","title":"diskover","permalink":"https://info.linuxserver.io/affected/diskover/","status":"ok","pages":[{"is":"issue","title":"Notification: Significant changes to cron incoming","createdAt":"2023-10-01 23:00:00 +0000 UTC","lastMod":"2023-10-01 10:32:41 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-10-01-cron/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","diskover","duckdns","feed2toot","freshrss","grav","lychee","nextcloud","rsnapshot","snipe-it","swag","transmission","webgrabplus"],"filename":"2023-10-01-cron.md"},{"is":"issue","title":"Notification: Significant changes to nginx based images","createdAt":"2022-08-20 18:00:00 +0000 UTC","lastMod":"2022-10-14 09:13:45 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2022-08-20-nginx-base/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","bookstack","cops","diskover","dokuwiki","freshrss","grav","grocy","heimdall","librespeed","lychee","muximux","nextcloud","nginx","photoshow","phpmyadmin","piwigo","pixapop","projectsend","snapdrop","snipe-it","swag","xbackbone"],"filename":"2022-08-20-nginx-base.md"},{"is":"issue","title":"New Container: Diskover","createdAt":"2018-11-01 00:00:00 +0000 UTC","lastMod":"2021-07-03 00:52:41 +0200 +0200","permalink":"https://info.linuxserver.io/issues/2018-11-01-diskover/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["New Containers","diskover"],"filename":"2018-11-01-diskover.md"}]}
|
||||
{"is":"system","title":"diskover","permalink":"https://info.linuxserver.io/affected/diskover/","status":"ok","pages":[{"is":"issue","title":"Notification: Significant changes to cron incoming","createdAt":"2023-10-20 23:00:00 +0000 UTC","lastMod":"2023-10-20 10:14:29 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-10-20-cron/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","diskover","duckdns","feed2toot","freshrss","grav","lychee","nextcloud","rsnapshot","snipe-it","swag","transmission","webgrabplus"],"filename":"2023-10-20-cron.md"},{"is":"issue","title":"Notification: Significant changes to cron incoming","createdAt":"2023-10-01 23:00:00 +0000 UTC","lastMod":"2023-10-01 10:32:41 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-10-01-cron/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","diskover","duckdns","feed2toot","freshrss","grav","lychee","nextcloud","rsnapshot","snipe-it","swag","transmission","webgrabplus"],"filename":"2023-10-01-cron.md"},{"is":"issue","title":"Notification: Significant changes to nginx based images","createdAt":"2022-08-20 18:00:00 +0000 UTC","lastMod":"2022-10-14 09:13:45 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2022-08-20-nginx-base/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","bookstack","cops","diskover","dokuwiki","freshrss","grav","grocy","heimdall","librespeed","lychee","muximux","nextcloud","nginx","photoshow","phpmyadmin","piwigo","pixapop","projectsend","snapdrop","snipe-it","swag","xbackbone"],"filename":"2022-08-20-nginx-base.md"},{"is":"issue","title":"New Container: Diskover","createdAt":"2018-11-01 00:00:00 +0000 UTC","lastMod":"2021-07-03 00:52:41 +0200 +0200","permalink":"https://info.linuxserver.io/issues/2018-11-01-diskover/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["New Containers","diskover"],"filename":"2018-11-01-diskover.md"}]}
|
||||
@ -1,4 +1,21 @@
|
||||
<?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-10-01T23:00:00+00:00</lastBuildDate><updated>2023-10-01T23: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 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.
|
||||
<?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-10-20T23:00:00+00:00</lastBuildDate><updated>2023-10-20T23: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 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>
|
||||
|
||||
File diff suppressed because one or more lines are too long
@ -1 +1 @@
|
||||
{"is":"system","title":"duckdns","permalink":"https://info.linuxserver.io/affected/duckdns/","status":"ok","pages":[{"is":"issue","title":"Notification: Significant changes to cron incoming","createdAt":"2023-10-01 23:00:00 +0000 UTC","lastMod":"2023-10-01 10:32:41 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-10-01-cron/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","diskover","duckdns","feed2toot","freshrss","grav","lychee","nextcloud","rsnapshot","snipe-it","swag","transmission","webgrabplus"],"filename":"2023-10-01-cron.md"},{"is":"issue","title":"New Container: Duckdns","createdAt":"2016-11-17 00:00:00 +0000 UTC","lastMod":"2021-07-03 00:52:41 +0200 +0200","permalink":"https://info.linuxserver.io/issues/2016-11-17-duckdns/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["New Containers","duckdns"],"filename":"2016-11-17-duckdns.md"}]}
|
||||
{"is":"system","title":"duckdns","permalink":"https://info.linuxserver.io/affected/duckdns/","status":"ok","pages":[{"is":"issue","title":"Notification: Significant changes to cron incoming","createdAt":"2023-10-20 23:00:00 +0000 UTC","lastMod":"2023-10-20 10:14:29 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-10-20-cron/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","diskover","duckdns","feed2toot","freshrss","grav","lychee","nextcloud","rsnapshot","snipe-it","swag","transmission","webgrabplus"],"filename":"2023-10-20-cron.md"},{"is":"issue","title":"Notification: Significant changes to cron incoming","createdAt":"2023-10-01 23:00:00 +0000 UTC","lastMod":"2023-10-01 10:32:41 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-10-01-cron/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","diskover","duckdns","feed2toot","freshrss","grav","lychee","nextcloud","rsnapshot","snipe-it","swag","transmission","webgrabplus"],"filename":"2023-10-01-cron.md"},{"is":"issue","title":"New Container: Duckdns","createdAt":"2016-11-17 00:00:00 +0000 UTC","lastMod":"2021-07-03 00:52:41 +0200 +0200","permalink":"https://info.linuxserver.io/issues/2016-11-17-duckdns/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["New Containers","duckdns"],"filename":"2016-11-17-duckdns.md"}]}
|
||||
@ -1,4 +1,21 @@
|
||||
<?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>duckdns on Info :: LinuxServer.io</title><link>https://info.linuxserver.io/affected/duckdns/</link><description>History</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2023-10-01T23:00:00+00:00</lastBuildDate><updated>2023-10-01T23:00:00+00:00</updated><atom:link href="https://info.linuxserver.io/affected/duckdns/index.xml" rel="self" type="application/rss+xml"/><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.
|
||||
<?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>duckdns on Info :: LinuxServer.io</title><link>https://info.linuxserver.io/affected/duckdns/</link><description>History</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2023-10-20T23:00:00+00:00</lastBuildDate><updated>2023-10-20T23:00:00+00:00</updated><atom:link href="https://info.linuxserver.io/affected/duckdns/index.xml" rel="self" type="application/rss+xml"/><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>
|
||||
|
||||
File diff suppressed because one or more lines are too long
@ -1 +1 @@
|
||||
{"is":"system","title":"feed2toot","permalink":"https://info.linuxserver.io/affected/feed2toot/","status":"ok","pages":[{"is":"issue","title":"Notification: Significant changes to cron incoming","createdAt":"2023-10-01 23:00:00 +0000 UTC","lastMod":"2023-10-01 10:32:41 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-10-01-cron/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","diskover","duckdns","feed2toot","freshrss","grav","lychee","nextcloud","rsnapshot","snipe-it","swag","transmission","webgrabplus"],"filename":"2023-10-01-cron.md"}]}
|
||||
{"is":"system","title":"feed2toot","permalink":"https://info.linuxserver.io/affected/feed2toot/","status":"ok","pages":[{"is":"issue","title":"Notification: Significant changes to cron incoming","createdAt":"2023-10-20 23:00:00 +0000 UTC","lastMod":"2023-10-20 10:14:29 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-10-20-cron/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","diskover","duckdns","feed2toot","freshrss","grav","lychee","nextcloud","rsnapshot","snipe-it","swag","transmission","webgrabplus"],"filename":"2023-10-20-cron.md"},{"is":"issue","title":"Notification: Significant changes to cron incoming","createdAt":"2023-10-01 23:00:00 +0000 UTC","lastMod":"2023-10-01 10:32:41 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-10-01-cron/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","diskover","duckdns","feed2toot","freshrss","grav","lychee","nextcloud","rsnapshot","snipe-it","swag","transmission","webgrabplus"],"filename":"2023-10-01-cron.md"}]}
|
||||
@ -1,4 +1,21 @@
|
||||
<?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>feed2toot on Info :: LinuxServer.io</title><link>https://info.linuxserver.io/affected/feed2toot/</link><description>History</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2023-10-01T23:00:00+00:00</lastBuildDate><updated>2023-10-01T23:00:00+00:00</updated><atom:link href="https://info.linuxserver.io/affected/feed2toot/index.xml" rel="self" type="application/rss+xml"/><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.
|
||||
<?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>feed2toot on Info :: LinuxServer.io</title><link>https://info.linuxserver.io/affected/feed2toot/</link><description>History</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2023-10-20T23:00:00+00:00</lastBuildDate><updated>2023-10-20T23:00:00+00:00</updated><atom:link href="https://info.linuxserver.io/affected/feed2toot/index.xml" rel="self" type="application/rss+xml"/><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>
|
||||
|
||||
File diff suppressed because one or more lines are too long
@ -1 +1 @@
|
||||
{"is":"system","title":"freshrss","permalink":"https://info.linuxserver.io/affected/freshrss/","status":"ok","pages":[{"is":"issue","title":"Notification: Significant changes to cron incoming","createdAt":"2023-10-01 23:00:00 +0000 UTC","lastMod":"2023-10-01 10:32:41 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-10-01-cron/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","diskover","duckdns","feed2toot","freshrss","grav","lychee","nextcloud","rsnapshot","snipe-it","swag","transmission","webgrabplus"],"filename":"2023-10-01-cron.md"},{"is":"issue","title":"Notification: Significant changes to nginx based images","createdAt":"2022-08-20 18:00:00 +0000 UTC","lastMod":"2022-10-14 09:13:45 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2022-08-20-nginx-base/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","bookstack","cops","diskover","dokuwiki","freshrss","grav","grocy","heimdall","librespeed","lychee","muximux","nextcloud","nginx","photoshow","phpmyadmin","piwigo","pixapop","projectsend","snapdrop","snipe-it","swag","xbackbone"],"filename":"2022-08-20-nginx-base.md"},{"is":"issue","title":"New Container: Freshrss","createdAt":"2015-08-21 00:00:00 +0000 UTC","lastMod":"2021-07-03 00:52:41 +0200 +0200","permalink":"https://info.linuxserver.io/issues/2015-08-21-freshrss/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["New Containers","freshrss"],"filename":"2015-08-21-freshrss.md"}]}
|
||||
{"is":"system","title":"freshrss","permalink":"https://info.linuxserver.io/affected/freshrss/","status":"ok","pages":[{"is":"issue","title":"Notification: Significant changes to cron incoming","createdAt":"2023-10-20 23:00:00 +0000 UTC","lastMod":"2023-10-20 10:14:29 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-10-20-cron/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","diskover","duckdns","feed2toot","freshrss","grav","lychee","nextcloud","rsnapshot","snipe-it","swag","transmission","webgrabplus"],"filename":"2023-10-20-cron.md"},{"is":"issue","title":"Notification: Significant changes to cron incoming","createdAt":"2023-10-01 23:00:00 +0000 UTC","lastMod":"2023-10-01 10:32:41 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-10-01-cron/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","diskover","duckdns","feed2toot","freshrss","grav","lychee","nextcloud","rsnapshot","snipe-it","swag","transmission","webgrabplus"],"filename":"2023-10-01-cron.md"},{"is":"issue","title":"Notification: Significant changes to nginx based images","createdAt":"2022-08-20 18:00:00 +0000 UTC","lastMod":"2022-10-14 09:13:45 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2022-08-20-nginx-base/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","bookstack","cops","diskover","dokuwiki","freshrss","grav","grocy","heimdall","librespeed","lychee","muximux","nextcloud","nginx","photoshow","phpmyadmin","piwigo","pixapop","projectsend","snapdrop","snipe-it","swag","xbackbone"],"filename":"2022-08-20-nginx-base.md"},{"is":"issue","title":"New Container: Freshrss","createdAt":"2015-08-21 00:00:00 +0000 UTC","lastMod":"2021-07-03 00:52:41 +0200 +0200","permalink":"https://info.linuxserver.io/issues/2015-08-21-freshrss/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["New Containers","freshrss"],"filename":"2015-08-21-freshrss.md"}]}
|
||||
@ -1,4 +1,21 @@
|
||||
<?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>freshrss on Info :: LinuxServer.io</title><link>https://info.linuxserver.io/affected/freshrss/</link><description>History</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2023-10-01T23:00:00+00:00</lastBuildDate><updated>2023-10-01T23:00:00+00:00</updated><atom:link href="https://info.linuxserver.io/affected/freshrss/index.xml" rel="self" type="application/rss+xml"/><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.
|
||||
<?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>freshrss on Info :: LinuxServer.io</title><link>https://info.linuxserver.io/affected/freshrss/</link><description>History</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2023-10-20T23:00:00+00:00</lastBuildDate><updated>2023-10-20T23:00:00+00:00</updated><atom:link href="https://info.linuxserver.io/affected/freshrss/index.xml" rel="self" type="application/rss+xml"/><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>
|
||||
|
||||
File diff suppressed because one or more lines are too long
@ -1 +1 @@
|
||||
{"is":"system","title":"grav","permalink":"https://info.linuxserver.io/affected/grav/","status":"ok","pages":[{"is":"issue","title":"Notification: Significant changes to cron incoming","createdAt":"2023-10-01 23:00:00 +0000 UTC","lastMod":"2023-10-01 10:32:41 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-10-01-cron/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","diskover","duckdns","feed2toot","freshrss","grav","lychee","nextcloud","rsnapshot","snipe-it","swag","transmission","webgrabplus"],"filename":"2023-10-01-cron.md"},{"is":"issue","title":"Notification: Significant changes to nginx based images","createdAt":"2022-08-20 18:00:00 +0000 UTC","lastMod":"2022-10-14 09:13:45 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2022-08-20-nginx-base/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","bookstack","cops","diskover","dokuwiki","freshrss","grav","grocy","heimdall","librespeed","lychee","muximux","nextcloud","nginx","photoshow","phpmyadmin","piwigo","pixapop","projectsend","snapdrop","snipe-it","swag","xbackbone"],"filename":"2022-08-20-nginx-base.md"},{"is":"issue","title":"New Container: Grav","createdAt":"2021-04-09 00:00:00 +0000 UTC","lastMod":"2021-07-03 00:52:41 +0200 +0200","permalink":"https://info.linuxserver.io/issues/2021-04-09-grav/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["New Containers","grav"],"filename":"2021-04-09-grav.md"}]}
|
||||
{"is":"system","title":"grav","permalink":"https://info.linuxserver.io/affected/grav/","status":"ok","pages":[{"is":"issue","title":"Notification: Significant changes to cron incoming","createdAt":"2023-10-20 23:00:00 +0000 UTC","lastMod":"2023-10-20 10:14:29 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-10-20-cron/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","diskover","duckdns","feed2toot","freshrss","grav","lychee","nextcloud","rsnapshot","snipe-it","swag","transmission","webgrabplus"],"filename":"2023-10-20-cron.md"},{"is":"issue","title":"Notification: Significant changes to cron incoming","createdAt":"2023-10-01 23:00:00 +0000 UTC","lastMod":"2023-10-01 10:32:41 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-10-01-cron/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","diskover","duckdns","feed2toot","freshrss","grav","lychee","nextcloud","rsnapshot","snipe-it","swag","transmission","webgrabplus"],"filename":"2023-10-01-cron.md"},{"is":"issue","title":"Notification: Significant changes to nginx based images","createdAt":"2022-08-20 18:00:00 +0000 UTC","lastMod":"2022-10-14 09:13:45 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2022-08-20-nginx-base/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","bookstack","cops","diskover","dokuwiki","freshrss","grav","grocy","heimdall","librespeed","lychee","muximux","nextcloud","nginx","photoshow","phpmyadmin","piwigo","pixapop","projectsend","snapdrop","snipe-it","swag","xbackbone"],"filename":"2022-08-20-nginx-base.md"},{"is":"issue","title":"New Container: Grav","createdAt":"2021-04-09 00:00:00 +0000 UTC","lastMod":"2021-07-03 00:52:41 +0200 +0200","permalink":"https://info.linuxserver.io/issues/2021-04-09-grav/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["New Containers","grav"],"filename":"2021-04-09-grav.md"}]}
|
||||
@ -1,4 +1,21 @@
|
||||
<?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>grav on Info :: LinuxServer.io</title><link>https://info.linuxserver.io/affected/grav/</link><description>History</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2023-10-01T23:00:00+00:00</lastBuildDate><updated>2023-10-01T23:00:00+00:00</updated><atom:link href="https://info.linuxserver.io/affected/grav/index.xml" rel="self" type="application/rss+xml"/><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.
|
||||
<?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>grav on Info :: LinuxServer.io</title><link>https://info.linuxserver.io/affected/grav/</link><description>History</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2023-10-20T23:00:00+00:00</lastBuildDate><updated>2023-10-20T23:00:00+00:00</updated><atom:link href="https://info.linuxserver.io/affected/grav/index.xml" rel="self" type="application/rss+xml"/><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>
|
||||
|
||||
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
@ -1 +1 @@
|
||||
{"is":"system","title":"lychee","permalink":"https://info.linuxserver.io/affected/lychee/","status":"ok","pages":[{"is":"issue","title":"Notification: Significant changes to cron incoming","createdAt":"2023-10-01 23:00:00 +0000 UTC","lastMod":"2023-10-01 10:32:41 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-10-01-cron/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","diskover","duckdns","feed2toot","freshrss","grav","lychee","nextcloud","rsnapshot","snipe-it","swag","transmission","webgrabplus"],"filename":"2023-10-01-cron.md"},{"is":"issue","title":"Notification: Significant changes to nginx based images","createdAt":"2022-08-20 18:00:00 +0000 UTC","lastMod":"2022-10-14 09:13:45 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2022-08-20-nginx-base/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","bookstack","cops","diskover","dokuwiki","freshrss","grav","grocy","heimdall","librespeed","lychee","muximux","nextcloud","nginx","photoshow","phpmyadmin","piwigo","pixapop","projectsend","snapdrop","snipe-it","swag","xbackbone"],"filename":"2022-08-20-nginx-base.md"},{"is":"issue","title":"New Container: Lychee","createdAt":"2017-02-12 00:00:00 +0000 UTC","lastMod":"2021-07-03 00:52:41 +0200 +0200","permalink":"https://info.linuxserver.io/issues/2017-02-12-lychee/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["New Containers","lychee"],"filename":"2017-02-12-lychee.md"}]}
|
||||
{"is":"system","title":"lychee","permalink":"https://info.linuxserver.io/affected/lychee/","status":"ok","pages":[{"is":"issue","title":"Notification: Significant changes to cron incoming","createdAt":"2023-10-20 23:00:00 +0000 UTC","lastMod":"2023-10-20 10:14:29 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-10-20-cron/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","diskover","duckdns","feed2toot","freshrss","grav","lychee","nextcloud","rsnapshot","snipe-it","swag","transmission","webgrabplus"],"filename":"2023-10-20-cron.md"},{"is":"issue","title":"Notification: Significant changes to cron incoming","createdAt":"2023-10-01 23:00:00 +0000 UTC","lastMod":"2023-10-01 10:32:41 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-10-01-cron/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","diskover","duckdns","feed2toot","freshrss","grav","lychee","nextcloud","rsnapshot","snipe-it","swag","transmission","webgrabplus"],"filename":"2023-10-01-cron.md"},{"is":"issue","title":"Notification: Significant changes to nginx based images","createdAt":"2022-08-20 18:00:00 +0000 UTC","lastMod":"2022-10-14 09:13:45 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2022-08-20-nginx-base/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","bookstack","cops","diskover","dokuwiki","freshrss","grav","grocy","heimdall","librespeed","lychee","muximux","nextcloud","nginx","photoshow","phpmyadmin","piwigo","pixapop","projectsend","snapdrop","snipe-it","swag","xbackbone"],"filename":"2022-08-20-nginx-base.md"},{"is":"issue","title":"New Container: Lychee","createdAt":"2017-02-12 00:00:00 +0000 UTC","lastMod":"2021-07-03 00:52:41 +0200 +0200","permalink":"https://info.linuxserver.io/issues/2017-02-12-lychee/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["New Containers","lychee"],"filename":"2017-02-12-lychee.md"}]}
|
||||
@ -1,4 +1,21 @@
|
||||
<?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>lychee on Info :: LinuxServer.io</title><link>https://info.linuxserver.io/affected/lychee/</link><description>History</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2023-10-01T23:00:00+00:00</lastBuildDate><updated>2023-10-01T23:00:00+00:00</updated><atom:link href="https://info.linuxserver.io/affected/lychee/index.xml" rel="self" type="application/rss+xml"/><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.
|
||||
<?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>lychee on Info :: LinuxServer.io</title><link>https://info.linuxserver.io/affected/lychee/</link><description>History</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2023-10-20T23:00:00+00:00</lastBuildDate><updated>2023-10-20T23:00:00+00:00</updated><atom:link href="https://info.linuxserver.io/affected/lychee/index.xml" rel="self" type="application/rss+xml"/><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>
|
||||
|
||||
File diff suppressed because one or more lines are too long
@ -1 +1 @@
|
||||
{"is":"system","title":"nextcloud","permalink":"https://info.linuxserver.io/affected/nextcloud/","status":"ok","pages":[{"is":"issue","title":"Notification: Significant changes to cron incoming","createdAt":"2023-10-01 23:00:00 +0000 UTC","lastMod":"2023-10-01 10:32:41 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-10-01-cron/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","diskover","duckdns","feed2toot","freshrss","grav","lychee","nextcloud","rsnapshot","snipe-it","swag","transmission","webgrabplus"],"filename":"2023-10-01-cron.md"},{"is":"issue","title":"Notification: Changes to our Nextcloud image","createdAt":"2023-06-25 22:00:00 +0000 UTC","lastMod":"2023-08-03 13:29:04 +0000 UTC","permalink":"https://info.linuxserver.io/issues/2023-06-25-nextcloud/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","nextcloud"],"filename":"2023-06-25-nextcloud.md"},{"is":"issue","title":"Nextcloud php8 Tag Deprecation Notice","createdAt":"2022-10-25 20:00:00 +0000 UTC","lastMod":"2022-10-25 18:07:30 +0100 +0100","permalink":"https://info.linuxserver.io/issues/2022-10-24-nextcloud/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Deprecations","nextcloud"],"filename":"2022-10-24-nextcloud.md"},{"is":"issue","title":"Notification: Significant changes to nginx based images","createdAt":"2022-08-20 18:00:00 +0000 UTC","lastMod":"2022-10-14 09:13:45 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2022-08-20-nginx-base/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","bookstack","cops","diskover","dokuwiki","freshrss","grav","grocy","heimdall","librespeed","lychee","muximux","nextcloud","nginx","photoshow","phpmyadmin","piwigo","pixapop","projectsend","snapdrop","snipe-it","swag","xbackbone"],"filename":"2022-08-20-nginx-base.md"},{"is":"issue","title":"New Container: Nextcloud","createdAt":"2017-03-07 00:00:00 +0000 UTC","lastMod":"2021-07-03 00:52:41 +0200 +0200","permalink":"https://info.linuxserver.io/issues/2017-03-07-nextcloud/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["New Containers","nextcloud"],"filename":"2017-03-07-nextcloud.md"}]}
|
||||
{"is":"system","title":"nextcloud","permalink":"https://info.linuxserver.io/affected/nextcloud/","status":"ok","pages":[{"is":"issue","title":"Notification: Significant changes to cron incoming","createdAt":"2023-10-20 23:00:00 +0000 UTC","lastMod":"2023-10-20 10:14:29 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-10-20-cron/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","diskover","duckdns","feed2toot","freshrss","grav","lychee","nextcloud","rsnapshot","snipe-it","swag","transmission","webgrabplus"],"filename":"2023-10-20-cron.md"},{"is":"issue","title":"Notification: Significant changes to cron incoming","createdAt":"2023-10-01 23:00:00 +0000 UTC","lastMod":"2023-10-01 10:32:41 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-10-01-cron/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","diskover","duckdns","feed2toot","freshrss","grav","lychee","nextcloud","rsnapshot","snipe-it","swag","transmission","webgrabplus"],"filename":"2023-10-01-cron.md"},{"is":"issue","title":"Notification: Changes to our Nextcloud image","createdAt":"2023-06-25 22:00:00 +0000 UTC","lastMod":"2023-08-03 13:29:04 +0000 UTC","permalink":"https://info.linuxserver.io/issues/2023-06-25-nextcloud/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","nextcloud"],"filename":"2023-06-25-nextcloud.md"},{"is":"issue","title":"Nextcloud php8 Tag Deprecation Notice","createdAt":"2022-10-25 20:00:00 +0000 UTC","lastMod":"2022-10-25 18:07:30 +0100 +0100","permalink":"https://info.linuxserver.io/issues/2022-10-24-nextcloud/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Deprecations","nextcloud"],"filename":"2022-10-24-nextcloud.md"},{"is":"issue","title":"Notification: Significant changes to nginx based images","createdAt":"2022-08-20 18:00:00 +0000 UTC","lastMod":"2022-10-14 09:13:45 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2022-08-20-nginx-base/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","bookstack","cops","diskover","dokuwiki","freshrss","grav","grocy","heimdall","librespeed","lychee","muximux","nextcloud","nginx","photoshow","phpmyadmin","piwigo","pixapop","projectsend","snapdrop","snipe-it","swag","xbackbone"],"filename":"2022-08-20-nginx-base.md"},{"is":"issue","title":"New Container: Nextcloud","createdAt":"2017-03-07 00:00:00 +0000 UTC","lastMod":"2021-07-03 00:52:41 +0200 +0200","permalink":"https://info.linuxserver.io/issues/2017-03-07-nextcloud/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["New Containers","nextcloud"],"filename":"2017-03-07-nextcloud.md"}]}
|
||||
@ -1,4 +1,21 @@
|
||||
<?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>nextcloud on Info :: LinuxServer.io</title><link>https://info.linuxserver.io/affected/nextcloud/</link><description>History</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2023-10-01T23:00:00+00:00</lastBuildDate><updated>2023-10-01T23:00:00+00:00</updated><atom:link href="https://info.linuxserver.io/affected/nextcloud/index.xml" rel="self" type="application/rss+xml"/><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.
|
||||
<?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>nextcloud on Info :: LinuxServer.io</title><link>https://info.linuxserver.io/affected/nextcloud/</link><description>History</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2023-10-20T23:00:00+00:00</lastBuildDate><updated>2023-10-20T23:00:00+00:00</updated><atom:link href="https://info.linuxserver.io/affected/nextcloud/index.xml" rel="self" type="application/rss+xml"/><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>
|
||||
|
||||
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
@ -1,4 +1,21 @@
|
||||
<?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>Notifications on Info :: LinuxServer.io</title><link>https://info.linuxserver.io/affected/notifications/</link><description>History</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2023-10-01T23:00:00+00:00</lastBuildDate><updated>2023-10-01T23:00:00+00:00</updated><atom:link href="https://info.linuxserver.io/affected/notifications/index.xml" rel="self" type="application/rss+xml"/><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.
|
||||
<?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>Notifications on Info :: LinuxServer.io</title><link>https://info.linuxserver.io/affected/notifications/</link><description>History</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2023-10-20T23:00:00+00:00</lastBuildDate><updated>2023-10-20T23:00:00+00:00</updated><atom:link href="https://info.linuxserver.io/affected/notifications/index.xml" rel="self" type="application/rss+xml"/><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>
|
||||
|
||||
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
@ -1 +1 @@
|
||||
{"is":"system","title":"rsnapshot","permalink":"https://info.linuxserver.io/affected/rsnapshot/","status":"ok","pages":[{"is":"issue","title":"Notification: Significant changes to cron incoming","createdAt":"2023-10-01 23:00:00 +0000 UTC","lastMod":"2023-10-01 10:32:41 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-10-01-cron/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","diskover","duckdns","feed2toot","freshrss","grav","lychee","nextcloud","rsnapshot","snipe-it","swag","transmission","webgrabplus"],"filename":"2023-10-01-cron.md"},{"is":"issue","title":"New Container: Rsnapshot","createdAt":"2020-08-20 00:00:00 +0000 UTC","lastMod":"2021-07-03 00:52:41 +0200 +0200","permalink":"https://info.linuxserver.io/issues/2020-08-20-rsnapshot/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["New Containers","rsnapshot"],"filename":"2020-08-20-rsnapshot.md"}]}
|
||||
{"is":"system","title":"rsnapshot","permalink":"https://info.linuxserver.io/affected/rsnapshot/","status":"ok","pages":[{"is":"issue","title":"Notification: Significant changes to cron incoming","createdAt":"2023-10-20 23:00:00 +0000 UTC","lastMod":"2023-10-20 10:14:29 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-10-20-cron/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","diskover","duckdns","feed2toot","freshrss","grav","lychee","nextcloud","rsnapshot","snipe-it","swag","transmission","webgrabplus"],"filename":"2023-10-20-cron.md"},{"is":"issue","title":"Notification: Significant changes to cron incoming","createdAt":"2023-10-01 23:00:00 +0000 UTC","lastMod":"2023-10-01 10:32:41 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-10-01-cron/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","diskover","duckdns","feed2toot","freshrss","grav","lychee","nextcloud","rsnapshot","snipe-it","swag","transmission","webgrabplus"],"filename":"2023-10-01-cron.md"},{"is":"issue","title":"New Container: Rsnapshot","createdAt":"2020-08-20 00:00:00 +0000 UTC","lastMod":"2021-07-03 00:52:41 +0200 +0200","permalink":"https://info.linuxserver.io/issues/2020-08-20-rsnapshot/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["New Containers","rsnapshot"],"filename":"2020-08-20-rsnapshot.md"}]}
|
||||
@ -1,4 +1,21 @@
|
||||
<?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>rsnapshot on Info :: LinuxServer.io</title><link>https://info.linuxserver.io/affected/rsnapshot/</link><description>History</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2023-10-01T23:00:00+00:00</lastBuildDate><updated>2023-10-01T23:00:00+00:00</updated><atom:link href="https://info.linuxserver.io/affected/rsnapshot/index.xml" rel="self" type="application/rss+xml"/><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.
|
||||
<?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>rsnapshot on Info :: LinuxServer.io</title><link>https://info.linuxserver.io/affected/rsnapshot/</link><description>History</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2023-10-20T23:00:00+00:00</lastBuildDate><updated>2023-10-20T23:00:00+00:00</updated><atom:link href="https://info.linuxserver.io/affected/rsnapshot/index.xml" rel="self" type="application/rss+xml"/><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>
|
||||
|
||||
File diff suppressed because one or more lines are too long
@ -1 +1 @@
|
||||
{"is":"system","title":"snipe-it","permalink":"https://info.linuxserver.io/affected/snipe-it/","status":"ok","pages":[{"is":"issue","title":"Notification: Significant changes to cron incoming","createdAt":"2023-10-01 23:00:00 +0000 UTC","lastMod":"2023-10-01 10:32:41 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-10-01-cron/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","diskover","duckdns","feed2toot","freshrss","grav","lychee","nextcloud","rsnapshot","snipe-it","swag","transmission","webgrabplus"],"filename":"2023-10-01-cron.md"},{"is":"issue","title":"Notification: Significant changes to nginx based images","createdAt":"2022-08-20 18:00:00 +0000 UTC","lastMod":"2022-10-14 09:13:45 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2022-08-20-nginx-base/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","bookstack","cops","diskover","dokuwiki","freshrss","grav","grocy","heimdall","librespeed","lychee","muximux","nextcloud","nginx","photoshow","phpmyadmin","piwigo","pixapop","projectsend","snapdrop","snipe-it","swag","xbackbone"],"filename":"2022-08-20-nginx-base.md"},{"is":"issue","title":"New Container: Snipe-It","createdAt":"2018-06-13 00:00:00 +0000 UTC","lastMod":"2021-07-03 00:52:41 +0200 +0200","permalink":"https://info.linuxserver.io/issues/2018-06-13-snipe-it/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["New Containers","snipe-it"],"filename":"2018-06-13-snipe-it.md"}]}
|
||||
{"is":"system","title":"snipe-it","permalink":"https://info.linuxserver.io/affected/snipe-it/","status":"ok","pages":[{"is":"issue","title":"Notification: Significant changes to cron incoming","createdAt":"2023-10-20 23:00:00 +0000 UTC","lastMod":"2023-10-20 10:14:29 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-10-20-cron/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","diskover","duckdns","feed2toot","freshrss","grav","lychee","nextcloud","rsnapshot","snipe-it","swag","transmission","webgrabplus"],"filename":"2023-10-20-cron.md"},{"is":"issue","title":"Notification: Significant changes to cron incoming","createdAt":"2023-10-01 23:00:00 +0000 UTC","lastMod":"2023-10-01 10:32:41 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-10-01-cron/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","diskover","duckdns","feed2toot","freshrss","grav","lychee","nextcloud","rsnapshot","snipe-it","swag","transmission","webgrabplus"],"filename":"2023-10-01-cron.md"},{"is":"issue","title":"Notification: Significant changes to nginx based images","createdAt":"2022-08-20 18:00:00 +0000 UTC","lastMod":"2022-10-14 09:13:45 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2022-08-20-nginx-base/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","bookstack","cops","diskover","dokuwiki","freshrss","grav","grocy","heimdall","librespeed","lychee","muximux","nextcloud","nginx","photoshow","phpmyadmin","piwigo","pixapop","projectsend","snapdrop","snipe-it","swag","xbackbone"],"filename":"2022-08-20-nginx-base.md"},{"is":"issue","title":"New Container: Snipe-It","createdAt":"2018-06-13 00:00:00 +0000 UTC","lastMod":"2021-07-03 00:52:41 +0200 +0200","permalink":"https://info.linuxserver.io/issues/2018-06-13-snipe-it/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["New Containers","snipe-it"],"filename":"2018-06-13-snipe-it.md"}]}
|
||||
@ -1,4 +1,21 @@
|
||||
<?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>snipe-it on Info :: LinuxServer.io</title><link>https://info.linuxserver.io/affected/snipe-it/</link><description>History</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2023-10-01T23:00:00+00:00</lastBuildDate><updated>2023-10-01T23:00:00+00:00</updated><atom:link href="https://info.linuxserver.io/affected/snipe-it/index.xml" rel="self" type="application/rss+xml"/><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.
|
||||
<?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>snipe-it on Info :: LinuxServer.io</title><link>https://info.linuxserver.io/affected/snipe-it/</link><description>History</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2023-10-20T23:00:00+00:00</lastBuildDate><updated>2023-10-20T23:00:00+00:00</updated><atom:link href="https://info.linuxserver.io/affected/snipe-it/index.xml" rel="self" type="application/rss+xml"/><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>
|
||||
|
||||
File diff suppressed because one or more lines are too long
@ -1 +1 @@
|
||||
{"is":"system","title":"swag","permalink":"https://info.linuxserver.io/affected/swag/","status":"ok","pages":[{"is":"issue","title":"Notification: Significant changes to cron incoming","createdAt":"2023-10-01 23:00:00 +0000 UTC","lastMod":"2023-10-01 10:32:41 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-10-01-cron/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","diskover","duckdns","feed2toot","freshrss","grav","lychee","nextcloud","rsnapshot","snipe-it","swag","transmission","webgrabplus"],"filename":"2023-10-01-cron.md"},{"is":"issue","title":"Notification: Significant changes to nginx based images","createdAt":"2022-08-20 18:00:00 +0000 UTC","lastMod":"2022-10-14 09:13:45 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2022-08-20-nginx-base/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","bookstack","cops","diskover","dokuwiki","freshrss","grav","grocy","heimdall","librespeed","lychee","muximux","nextcloud","nginx","photoshow","phpmyadmin","piwigo","pixapop","projectsend","snapdrop","snipe-it","swag","xbackbone"],"filename":"2022-08-20-nginx-base.md"},{"is":"issue","title":"Authelia Vulnerability","createdAt":"2021-05-30 00:00:00 +0000 UTC","lastMod":"2021-05-30 16:53:02 +0100 +0100","permalink":"https://info.linuxserver.io/issues/2021-05-30-authelia/","severity":"notice","resolved":true,"informational":false,"resolvedAt":"2021-05-30","affected":["Vulnerabilities","authelia","swag"],"filename":"2021-05-30-authelia.md"},{"is":"issue","title":"Known Issue: Swag 1.15.0","createdAt":"2021-05-29 00:00:00 +0000 UTC","lastMod":"2021-06-02 20:51:38 +0100 +0100","permalink":"https://info.linuxserver.io/issues/2021-05-29-swag/","severity":"notice","resolved":true,"informational":false,"resolvedAt":"2021-06-02","affected":["Known Issues","swag"],"filename":"2021-05-29-swag.md"},{"is":"issue","title":"New Container: Swag","createdAt":"2020-08-03 00:00:00 +0000 UTC","lastMod":"2021-07-03 00:52:41 +0200 +0200","permalink":"https://info.linuxserver.io/issues/2020-08-03-swag/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["New Containers","swag"],"filename":"2020-08-03-swag.md"}]}
|
||||
{"is":"system","title":"swag","permalink":"https://info.linuxserver.io/affected/swag/","status":"ok","pages":[{"is":"issue","title":"Notification: Significant changes to cron incoming","createdAt":"2023-10-20 23:00:00 +0000 UTC","lastMod":"2023-10-20 10:14:29 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-10-20-cron/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","diskover","duckdns","feed2toot","freshrss","grav","lychee","nextcloud","rsnapshot","snipe-it","swag","transmission","webgrabplus"],"filename":"2023-10-20-cron.md"},{"is":"issue","title":"Notification: Significant changes to cron incoming","createdAt":"2023-10-01 23:00:00 +0000 UTC","lastMod":"2023-10-01 10:32:41 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-10-01-cron/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","diskover","duckdns","feed2toot","freshrss","grav","lychee","nextcloud","rsnapshot","snipe-it","swag","transmission","webgrabplus"],"filename":"2023-10-01-cron.md"},{"is":"issue","title":"Notification: Significant changes to nginx based images","createdAt":"2022-08-20 18:00:00 +0000 UTC","lastMod":"2022-10-14 09:13:45 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2022-08-20-nginx-base/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","bookstack","cops","diskover","dokuwiki","freshrss","grav","grocy","heimdall","librespeed","lychee","muximux","nextcloud","nginx","photoshow","phpmyadmin","piwigo","pixapop","projectsend","snapdrop","snipe-it","swag","xbackbone"],"filename":"2022-08-20-nginx-base.md"},{"is":"issue","title":"Authelia Vulnerability","createdAt":"2021-05-30 00:00:00 +0000 UTC","lastMod":"2021-05-30 16:53:02 +0100 +0100","permalink":"https://info.linuxserver.io/issues/2021-05-30-authelia/","severity":"notice","resolved":true,"informational":false,"resolvedAt":"2021-05-30","affected":["Vulnerabilities","authelia","swag"],"filename":"2021-05-30-authelia.md"},{"is":"issue","title":"Known Issue: Swag 1.15.0","createdAt":"2021-05-29 00:00:00 +0000 UTC","lastMod":"2021-06-02 20:51:38 +0100 +0100","permalink":"https://info.linuxserver.io/issues/2021-05-29-swag/","severity":"notice","resolved":true,"informational":false,"resolvedAt":"2021-06-02","affected":["Known Issues","swag"],"filename":"2021-05-29-swag.md"},{"is":"issue","title":"New Container: Swag","createdAt":"2020-08-03 00:00:00 +0000 UTC","lastMod":"2021-07-03 00:52:41 +0200 +0200","permalink":"https://info.linuxserver.io/issues/2020-08-03-swag/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["New Containers","swag"],"filename":"2020-08-03-swag.md"}]}
|
||||
@ -1,4 +1,21 @@
|
||||
<?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>swag on Info :: LinuxServer.io</title><link>https://info.linuxserver.io/affected/swag/</link><description>History</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2023-10-01T23:00:00+00:00</lastBuildDate><updated>2023-10-01T23:00:00+00:00</updated><atom:link href="https://info.linuxserver.io/affected/swag/index.xml" rel="self" type="application/rss+xml"/><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.
|
||||
<?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>swag on Info :: LinuxServer.io</title><link>https://info.linuxserver.io/affected/swag/</link><description>History</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2023-10-20T23:00:00+00:00</lastBuildDate><updated>2023-10-20T23:00:00+00:00</updated><atom:link href="https://info.linuxserver.io/affected/swag/index.xml" rel="self" type="application/rss+xml"/><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>
|
||||
|
||||
File diff suppressed because one or more lines are too long
@ -1 +1 @@
|
||||
{"is":"system","title":"transmission","permalink":"https://info.linuxserver.io/affected/transmission/","status":"ok","pages":[{"is":"issue","title":"Notification: Significant changes to cron incoming","createdAt":"2023-10-01 23:00:00 +0000 UTC","lastMod":"2023-10-01 10:32:41 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-10-01-cron/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","diskover","duckdns","feed2toot","freshrss","grav","lychee","nextcloud","rsnapshot","snipe-it","swag","transmission","webgrabplus"],"filename":"2023-10-01-cron.md"},{"is":"issue","title":"New Container: Transmission","createdAt":"2015-11-16 00:00:00 +0000 UTC","lastMod":"2021-07-03 00:52:41 +0200 +0200","permalink":"https://info.linuxserver.io/issues/2015-11-16-transmission/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["New Containers","transmission"],"filename":"2015-11-16-transmission.md"}]}
|
||||
{"is":"system","title":"transmission","permalink":"https://info.linuxserver.io/affected/transmission/","status":"ok","pages":[{"is":"issue","title":"Notification: Significant changes to cron incoming","createdAt":"2023-10-20 23:00:00 +0000 UTC","lastMod":"2023-10-20 10:14:29 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-10-20-cron/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","diskover","duckdns","feed2toot","freshrss","grav","lychee","nextcloud","rsnapshot","snipe-it","swag","transmission","webgrabplus"],"filename":"2023-10-20-cron.md"},{"is":"issue","title":"Notification: Significant changes to cron incoming","createdAt":"2023-10-01 23:00:00 +0000 UTC","lastMod":"2023-10-01 10:32:41 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-10-01-cron/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","diskover","duckdns","feed2toot","freshrss","grav","lychee","nextcloud","rsnapshot","snipe-it","swag","transmission","webgrabplus"],"filename":"2023-10-01-cron.md"},{"is":"issue","title":"New Container: Transmission","createdAt":"2015-11-16 00:00:00 +0000 UTC","lastMod":"2021-07-03 00:52:41 +0200 +0200","permalink":"https://info.linuxserver.io/issues/2015-11-16-transmission/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["New Containers","transmission"],"filename":"2015-11-16-transmission.md"}]}
|
||||
@ -1,4 +1,21 @@
|
||||
<?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>transmission on Info :: LinuxServer.io</title><link>https://info.linuxserver.io/affected/transmission/</link><description>History</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2023-10-01T23:00:00+00:00</lastBuildDate><updated>2023-10-01T23:00:00+00:00</updated><atom:link href="https://info.linuxserver.io/affected/transmission/index.xml" rel="self" type="application/rss+xml"/><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.
|
||||
<?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>transmission on Info :: LinuxServer.io</title><link>https://info.linuxserver.io/affected/transmission/</link><description>History</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2023-10-20T23:00:00+00:00</lastBuildDate><updated>2023-10-20T23:00:00+00:00</updated><atom:link href="https://info.linuxserver.io/affected/transmission/index.xml" rel="self" type="application/rss+xml"/><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>
|
||||
|
||||
File diff suppressed because one or more lines are too long
@ -1 +1 @@
|
||||
{"is":"system","title":"webgrabplus","permalink":"https://info.linuxserver.io/affected/webgrabplus/","status":"ok","pages":[{"is":"issue","title":"Notification: Significant changes to cron incoming","createdAt":"2023-10-01 23:00:00 +0000 UTC","lastMod":"2023-10-01 10:32:41 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-10-01-cron/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","diskover","duckdns","feed2toot","freshrss","grav","lychee","nextcloud","rsnapshot","snipe-it","swag","transmission","webgrabplus"],"filename":"2023-10-01-cron.md"},{"is":"issue","title":"New Container: Webgrabplus","createdAt":"2018-01-18 00:00:00 +0000 UTC","lastMod":"2021-07-03 00:52:41 +0200 +0200","permalink":"https://info.linuxserver.io/issues/2018-01-18-webgrabplus/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["New Containers","webgrabplus"],"filename":"2018-01-18-webgrabplus.md"}]}
|
||||
{"is":"system","title":"webgrabplus","permalink":"https://info.linuxserver.io/affected/webgrabplus/","status":"ok","pages":[{"is":"issue","title":"Notification: Significant changes to cron incoming","createdAt":"2023-10-20 23:00:00 +0000 UTC","lastMod":"2023-10-20 10:14:29 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-10-20-cron/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","diskover","duckdns","feed2toot","freshrss","grav","lychee","nextcloud","rsnapshot","snipe-it","swag","transmission","webgrabplus"],"filename":"2023-10-20-cron.md"},{"is":"issue","title":"Notification: Significant changes to cron incoming","createdAt":"2023-10-01 23:00:00 +0000 UTC","lastMod":"2023-10-01 10:32:41 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-10-01-cron/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","diskover","duckdns","feed2toot","freshrss","grav","lychee","nextcloud","rsnapshot","snipe-it","swag","transmission","webgrabplus"],"filename":"2023-10-01-cron.md"},{"is":"issue","title":"New Container: Webgrabplus","createdAt":"2018-01-18 00:00:00 +0000 UTC","lastMod":"2021-07-03 00:52:41 +0200 +0200","permalink":"https://info.linuxserver.io/issues/2018-01-18-webgrabplus/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["New Containers","webgrabplus"],"filename":"2018-01-18-webgrabplus.md"}]}
|
||||
@ -1,4 +1,21 @@
|
||||
<?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>webgrabplus on Info :: LinuxServer.io</title><link>https://info.linuxserver.io/affected/webgrabplus/</link><description>History</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2023-10-01T23:00:00+00:00</lastBuildDate><updated>2023-10-01T23:00:00+00:00</updated><atom:link href="https://info.linuxserver.io/affected/webgrabplus/index.xml" rel="self" type="application/rss+xml"/><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.
|
||||
<?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>webgrabplus on Info :: LinuxServer.io</title><link>https://info.linuxserver.io/affected/webgrabplus/</link><description>History</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2023-10-20T23:00:00+00:00</lastBuildDate><updated>2023-10-20T23:00:00+00:00</updated><atom:link href="https://info.linuxserver.io/affected/webgrabplus/index.xml" rel="self" type="application/rss+xml"/><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>
|
||||
|
||||
@ -16,7 +16,9 @@
|
||||
<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>var highestLevelStatus,highestLevelStatusReadable;thisCategory=document.currentScript.parentNode,componentsOfThisCategory=thisCategory.querySelectorAll('.component'),highestLevelStatus='';function checkStatus(b){var a=b.getAttribute('data-status');a==='down'?highestLevelStatus='down':a==='disrupted'&&highestLevelStatus!=='down'?highestLevelStatus='disrupted':a==='notice'&&highestLevelStatus!=='down'&&highestLevelStatus!=='disrupted'&&(highestLevelStatus='notice')}componentsOfThisCategory.forEach(a=>checkStatus(a)),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-2023><a href=#archive-2023 class=no-underline><strong>2023</strong>
|
||||
<span class=faded>(40)</span></a></p><a href=https://info.linuxserver.io/issues/2023-10-17-headphones/ class="issue no-underline"><small class="date float-right relative-time" title="Oct 17 21:00:00 2023 UTC">October 17, 2023 at 9:00 PM</small><h3>Headphones Deprecation Notice ℹ</h3><span class=faded>Due to compatibility and build issues caused by a lack of upstream development, we have decided to deprecate our Headphones container.</span></a>
|
||||
<span class=faded>(41)</span></a></p><a href=https://info.linuxserver.io/issues/2023-10-20-cron/ class="issue no-underline"><small class="date float-right relative-time" title="Oct 20 23:00:00 2023 UTC">October 20, 2023 at 11:00 PM</small><h3>Notification: Significant changes to cron incoming ℹ</h3><span class=faded>We’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 …</span></a>
|
||||
<a href=https://info.linuxserver.io/issues/2023-10-17-headphones/ class="issue no-underline"><small class="date float-right relative-time" title="Oct 17 21:00:00 2023 UTC">October 17, 2023 at 9:00 PM</small><h3>Headphones Deprecation Notice ℹ</h3><span class=faded>Due to compatibility and build issues caused by a lack of upstream development, we have decided to deprecate our Headphones container.</span></a>
|
||||
<a href=https://info.linuxserver.io/issues/2023-10-01-cron/ class="issue no-underline"><small class="date float-right relative-time" title="Oct 1 23:00:00 2023 UTC">October 1, 2023 at 11:00 PM</small><h3>Notification: Significant changes to cron incoming ℹ</h3><span class=faded>We’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 …</span></a>
|
||||
<a href=https://info.linuxserver.io/issues/2023-09-18-series-troxide/ class="issue no-underline"><small class="date float-right relative-time" title="Sep 18 21:00:00 2023 UTC">September 18, 2023 at 9:00 PM</small><h3>New Container: Series Troxide ℹ</h3><span class=faded>We have released a new container for Series Troxide!
|
||||
|
||||
@ -1 +1 @@
|
||||
{"is":"index","cStateVersion":"5.5.2","apiVersion":"2.0","title":"Info :: LinuxServer.io","languageCodeHTML":"en","languageCode":"en","baseURL":"https://info.linuxserver.io","description":"<no value>","summaryStatus":"notice","categories":[{"name":"Images","description":"Information regarding our images","hideTitle":false,"closedByDefault":false},{"name":"Security","hideTitle":false,"closedByDefault":false}],"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":"notice","unresolvedIssues":[{"is":"issue","title":"Known Issue: Portainer & Synology Docker UI","createdAt":"2023-05-22 12:00:00 +0000 UTC","lastMod":"2023-05-22 14:22:54 +0100 +0100","permalink":"https://info.linuxserver.io/issues/2023-05-22-portainer/","severity":"notice","resolved":false,"informational":false,"resolvedAt":"<no value>","affected":["Known Issues","portainer","synology"],"filename":"2023-05-22-portainer.md"}]},{"name":"Notifications","category":"Images","status":"ok","unresolvedIssues":[]}],"buildDate":"2023-10-17","buildTime":"13:09","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.5.2","apiVersion":"2.0","title":"Info :: LinuxServer.io","languageCodeHTML":"en","languageCode":"en","baseURL":"https://info.linuxserver.io","description":"<no value>","summaryStatus":"notice","categories":[{"name":"Images","description":"Information regarding our images","hideTitle":false,"closedByDefault":false},{"name":"Security","hideTitle":false,"closedByDefault":false}],"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":"notice","unresolvedIssues":[{"is":"issue","title":"Known Issue: Portainer & Synology Docker UI","createdAt":"2023-05-22 12:00:00 +0000 UTC","lastMod":"2023-05-22 14:22:54 +0100 +0100","permalink":"https://info.linuxserver.io/issues/2023-05-22-portainer/","severity":"notice","resolved":false,"informational":false,"resolvedAt":"<no value>","affected":["Known Issues","portainer","synology"],"filename":"2023-05-22-portainer.md"}]},{"name":"Notifications","category":"Images","status":"ok","unresolvedIssues":[]}],"buildDate":"2023-10-20","buildTime":"16:06","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"}
|
||||
17
index.xml
17
index.xml
@ -1,4 +1,19 @@
|
||||
<?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>Tue, 17 Oct 2023 21:00:00 +0000</lastBuildDate><atom:link href="https://info.linuxserver.io/index.xml" rel="self" type="application/rss+xml"/><item><title>Headphones Deprecation Notice</title><link>https://info.linuxserver.io/issues/2023-10-17-headphones/</link><pubDate>Tue, 17 Oct 2023 21:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2023-10-17-headphones/</guid><category/><description><p>Due to compatibility and build issues caused by a lack of upstream development, we have decided to deprecate our <a href="https://github.com/linuxserver/docker-headphones">Headphones</a> container.</p></description></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><p>We&rsquo;ve decided to make some changes to how cron is shipped in our images.</p>
|
||||
<?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, 20 Oct 2023 23:00:00 +0000</lastBuildDate><atom:link href="https://info.linuxserver.io/index.xml" rel="self" type="application/rss+xml"/><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><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></description></item><item><title>Headphones Deprecation Notice</title><link>https://info.linuxserver.io/issues/2023-10-17-headphones/</link><pubDate>Tue, 17 Oct 2023 21:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2023-10-17-headphones/</guid><category/><description><p>Due to compatibility and build issues caused by a lack of upstream development, we have decided to deprecate our <a href="https://github.com/linuxserver/docker-headphones">Headphones</a> container.</p></description></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><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>
|
||||
|
||||
19
issues/2023-10-20-cron/index.html
Normal file
19
issues/2023-10-20-cron/index.html
Normal file
File diff suppressed because one or more lines are too long
1
issues/2023-10-20-cron/index.json
Normal file
1
issues/2023-10-20-cron/index.json
Normal file
@ -0,0 +1 @@
|
||||
{"is":"issue","title":"Notification: Significant changes to cron incoming","createdAt":"2023-10-20 23:00:00 +0000 UTC","lastMod":"2023-10-20 10:14:29 -0500 -0500","permalink":"https://info.linuxserver.io/issues/2023-10-20-cron/","severity":"<no value>","resolved":false,"informational":true,"resolvedAt":"<no value>","affected":["Notifications","diskover","duckdns","feed2toot","freshrss","grav","lychee","nextcloud","rsnapshot","snipe-it","swag","transmission","webgrabplus"],"filename":"2023-10-20-cron.md"}
|
||||
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
@ -1,4 +1,21 @@
|
||||
<?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>Issues on Info :: LinuxServer.io</title><link>https://info.linuxserver.io/issues/</link><description>History</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2023-10-17T21:00:00+00:00</lastBuildDate><updated>2023-10-17T21:00:00+00:00</updated><atom:link href="https://info.linuxserver.io/issues/index.xml" rel="self" type="application/rss+xml"/><item><title>Headphones Deprecation Notice</title><link>https://info.linuxserver.io/issues/2023-10-17-headphones/</link><pubDate>Tue, 17 Oct 2023 21:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2023-10-17-headphones/</guid><category/><description>Due to compatibility and build issues caused by a lack of upstream development, we have decided to deprecate our Headphones container.</description><content type="html"><p>Due to compatibility and build issues caused by a lack of upstream development, we have decided to deprecate our <a href="https://github.com/linuxserver/docker-headphones">Headphones</a> container.</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.
|
||||
<?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>Issues on Info :: LinuxServer.io</title><link>https://info.linuxserver.io/issues/</link><description>History</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2023-10-20T23:00:00+00:00</lastBuildDate><updated>2023-10-20T23:00:00+00:00</updated><atom:link href="https://info.linuxserver.io/issues/index.xml" rel="self" type="application/rss+xml"/><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>Headphones Deprecation Notice</title><link>https://info.linuxserver.io/issues/2023-10-17-headphones/</link><pubDate>Tue, 17 Oct 2023 21:00:00 +0000</pubDate><guid>https://info.linuxserver.io/issues/2023-10-17-headphones/</guid><category/><description>Due to compatibility and build issues caused by a lack of upstream development, we have decided to deprecate our Headphones container.</description><content type="html"><p>Due to compatibility and build issues caused by a lack of upstream development, we have decided to deprecate our <a href="https://github.com/linuxserver/docker-headphones">Headphones</a> container.</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>
|
||||
|
||||
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
Loading…
x
Reference in New Issue
Block a user