To ensure you don't miss it, I repeat DO NOT try to skip Debian releases - it will definitely cause issues! The steps are similarly documented in the in the specific section of the Debian Bullseye/11 Release Notes.
#Update debian upgrade#
You must go Stretch/9 -> Buster/10 -> Bullseye/11.Įverything I've noted above re the upgrade to Buster, will also generally apply to upgrading to Bullseye. DON'T try to upgrade from Stretch/9 -> Bullseye/11!. That is a Buster/10 -> Bullseye/11 upgrade too!? Note that you must do the upgrades in order of release - i.e. Once you've done the Stretch/9 -> Buster/10 upgrade successfully and everything is working as it should, you could consider going the next step. It may even be best to do a trial upgrade in a separate VM created from a snapshot of the current server before you do it for real? There's no option to rollback a failed Debian upgrade, so if it fails completely, you'll need to be sure you can go back to your original state.
#Update debian full#
Obviously, don't do that on your production machine unless you have a full OS backup/snapshot. Please note though, that explicitly covers upgrade from Buster -> Bullseye, so be sure to change the CODENAME appropriately (to 'buster').
#Update debian how to#
I have previously posted instructions on how to do that. You'll need to ensure that you have all the right keys. The only bit that might catch you up is the way that the TurnKey repository signing keys are managed now. Worst case scenario, following the Debian docs should get you over the line. I suggest that you also do an internet search for something like "upgrade debian stretch to buster" for some less convoluted and explicit instructions on upgrading to give you some more ideas about that. It's probably a bit over the top really and a number of steps can probably safely be skipped. The best and most complete documentation on doing a Stretch -> Buster upgrade can be found in the specific section of the Debian Buster/10 Release Notes. And anything that is an issue, I can assist you to fix (hopefully). The downside is that you won't get all of the tweaks that we apply to the newer releases.
I'm also happy to do my best to help out if you get stuck. Many others have done it and no major issues have been reported, so you should be good. We don't explicitly do anything that should cause issues with the process though, so I would expect it to work fine. Technically we don't support "in place" upgrades, but that's only because we don't have the spare cycles to exhaustively test that pathway. The other option is to do a Debian style "in place" OS upgrade. I do hope to resolve that at some point, but it does make this option a bit problematic at the moment. Although we haven't maintained our GitLab appliance due to the issues we've had with it and the high maintenance overhead. The first option is our general recommendation and essentially what you've done before. Migrate your data to a newer release of the same server.In the general case of TurnKey, you have 2 options:
0 kommentar(er)
