4 ms·
> This is because canonical insists on auto-updating and refreshing the snap at random intervals, even when you pin to a specific version channel. You can cont
by rlpb 5y ago
> This is because canonical insists on auto-updating and refreshing the snap at random intervals, even when you pin to a specific version channel.
You can control snap updates to match your maintenance windows, or just defer them. Documentation here: https://snapcraft.io/docs/keeping-snaps-up-to-date#heading--controlling-updates https://snapcraft.io/docs/keeping-snaps-up-to-date#heading--...
What you cannot do without patching is defer an update for more than 90 days. [Edit: well, you sort of can, by bypassing the store and "sideloading" instead: https://forum.snapcraft.io/t/disabling-automatic-refresh-for-snap-from-store/707/269 https://forum.snapcraft.io/t/disabling-automatic-refresh-for...]
- alyandon 5y agoWhy would any sysadmin that maintains a fleet of servers with varying maintenance windows (that may or may not be dependent on the packages installed) want to feed snapd a list of dates and times to basically ask it pretty please not to auto-update snaps? It is much easier to give sysadmins back the power they've always had to perform updates when it is reasonable to do so on their own schedule without having to inform snapd of what that schedule is. I really don't appreciate being told by Canonical that I have to jump through additional hoops and spend additional time satisfying snapd to maintain the systems under my control.
- donmcronald 5y agoMy initial reaction was that having schedules upgrades like that would be great, but then 5 seconds later I realized it's much better suited to Cron, SystemD, Ansible (etc.). I think the reason for auto-updates like this is because selling the control back to us is the business plan. It's the same thing Microsoft does.