pveupdate
and pveupgrade
Not sure but you should never useHi
pveupdate and pveupgrade it's the same thing to give apt update and apt upgrade?
apt upgrade
. But a apt update && apt dist-upgrade -y
or apt update && apt full-upgrade -y
should be fine.apt upgrade
or apt dist-upgrade
. Its also not that easy to automate PVE host backups, so I still do my PVE/PBS host upgrades manually on a weekly basis.reboot
. So you could pipe the output of apt update && apt full-upgrade -y
into something like grep to filter out a line that suggests you to reboot your host and if that line is found you could use a if
to optionally add a reboot
.Not sure but you should never useapt upgrade
. But aapt update && apt dist-upgrade -y
orapt update && apt full-upgrade -y
should be fine.
Debian also got the unattended-upgrades package that I use in all my Debian VMs to just autoupgrade security fixes, but not sure if that actually will useapt upgrade
orapt dist-upgrade
. Its also not that easy to automate PVE host backups, so I still do my PVE/PBS host upgrades manually on a weekly basis.
apt upgrade
? I typically run apt-get update -y && apt-get upgrade -y
to keep things up to date.don't use apt-get upgrade will proxmox ! use apt dist-upgrade.Sorry to revive an old thread, but why neverapt upgrade
? I typically runapt-get update -y && apt-get upgrade -y
to keep things up to date.
Thanks for the info, that makes complete sense. Sounds like dist-upgrade and full-upgrade to the same thing, according to this comment below, but I'll use dist-upgrade since that seems to be the "smartest".don't use apt-get upgrade will proxmox ! use apt dist-upgrade.
The difference between both is that "upgrade" only upgrade current installed packages. But if a package (like qemu), need a new dependencie, "upgrade" will not installed it. (so it'll break your proxmox installation).
This is working fine with a "stable" distro like debian, because you never have newer packages in the debian repo until the next debian major version.
Proxmox is more dynamic, some new packages can be needed between minor versions.
Using "dist-upgrade" , upgrade current packages + install new dependencies packages if needed.
many thanks - yes I do lxc container backups 3 times a week at least keeping the last 4, to 2 different drives (1 usb mounted hdd and another HDD on a different PC)Here I always install unattended-upgrades for all VMs and LXCs but not for the PVE host itself and that worked perfectly fine so far. But I wouldn't use it for the PVE host, as you are more likely to break something and you probably don't have host backups that are super up-to-date to restore a PVE installation from right before the upgrade. Also keep in mind that you can't downgrade a PVE installation once upgraded.
And for my VMs/LXCs I only want to auto upgrade security updates and not regular updates. So security holes get closed fast but no updates, that add new features and therefore are more likely to break something, will be auto installed.
And its always a good idea to have daily backups and hourly snapshots. In case something went wrong and the guest won't run anymore, you can restore a snapshot from yesterday or rollback to the hour before the auto upgrade.
Once per week I then manually upgrade small normal upgrades (patch level). And once per month I do the big upgrades (major and minor level upgrades). But right before that I create a backup and right after the upgrade I test everything in short if it still works. And if not I will restore the backup I did some minutes earlier.
I think thats a good workflow for a homelab. For production you might even be more strict and use test systems to verify first that the upgrade is save before rolling out the upgrades to the production systems using ansible.
great - like this one?The PVE host uses postfix to send backup notification emails. So you need to setup your postfix server. Same for all your guests. If you want them to send emails you will have to install a email server inside each guest.
But how to setup postfix as a sattelite system really depends on your SMTP provider. Basically each SMTP provider requires a dofferent config. If it doesn't peredtly match the public SMTP server will just drop your emails and won't relay them.
So best to google for tutorials "postfix tutorial YourMailProviderName".
I think for the host, but if you want your guests to send emails too, you would have to do the same thing inside each guest.great - like this one?
https://forum.proxmox.com/threads/get-postfix-to-send-notifications-email-externally.59940/
Now a daft question are these commands/files on the proxmox host or within each guest(lxc container)?
Thanks I'll certainly look into that option alsoI personally only setup postfix on my host because I was too annoyed to set it up for dozens of guests.
Instead I setup filebeat and zabbix-agent inside my guests so I got centralized metrics monitoring using a Zabbix LXC and centralized logging using a Graylog LXC. With that notification mails aren't really needed anymore as I can directly monitor the apt logs for failures and check if upgrades are available through the Graylog and Zabbix webUIs.