-
Notifications
You must be signed in to change notification settings - Fork 4
Add instructions to upgrade the Sprite OS #159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,44 @@ | ||
| --- | ||
| title: Sprite Maintenance | ||
| description: Keeping your Sprites happy and healthy | ||
| --- | ||
|
|
||
| import { Callout, StatusIcon } from '@/components/react'; | ||
|
|
||
| Sprites are persistent. Everything you leave is there when you come back, including the software. Long-living Sprites still need regular updates. This guide walks through some of the common tasks for maintaining the software environment in your Sprite. | ||
|
|
||
| --- | ||
|
|
||
| ## OS Upgrades | ||
|
|
||
| New Sprites run on a fresh install of Ubuntu 25.10. Older Sprites created with Ubuntu 25.04 must upgrade to continue receiving security and feature updates. | ||
|
|
||
| <Callout type="info"> | ||
| If you don't know what version of Ubuntu your Sprite currently runs, check with: | ||
|
|
||
| ```bash | ||
| lsb_release -d | ||
| ``` | ||
| </Callout> | ||
|
|
||
| Fortunately, Sprites are disposable. If your workload doesn't require the Sprite to live long-term, upgrading is easy: destroy the Sprite and create a new one! If you need to copy files over, try [mounting the filesystem locally](/working-with-sprites/#mounting-filesystem-locally). | ||
|
|
||
| If creating a new Sprite is impractical, you can also upgrade Ubuntu in-place. Keep in mind that bundled software (such as agents and language toolchains) must be upgraded separately. Install the Ubuntu upgrader with: | ||
|
Check warning on line 26 in src/content/docs/sprite-maintenance.mdx
|
||
|
|
||
| ```bash | ||
| sudo apt update | ||
| sudo apt install ubuntu-release-upgrader-core | ||
| ``` | ||
|
|
||
| With the upgrader installed, follow the [official instructions](https://ubuntu.com/server/docs/how-to/software/upgrade-your-release/) from Ubuntu. In short: | ||
|
Check warning on line 33 in src/content/docs/sprite-maintenance.mdx
|
||
|
|
||
| ```bash | ||
| # upgrade to the latest packages for the current release | ||
| sudo apt upgrade | ||
|
|
||
| # switch to the new release | ||
| sudo do-release-upgrade | ||
|
|
||
| # upgrade installed packages to the new release | ||
| sudo apt upgrade | ||
| ``` | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we assume our users know how to upgrade their bundled software/agents and language toolchains, or give some kind of hint how they would do that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't have a plan yet and mostly mentioned it as a nudge that creating a new Sprite is the better way. Every toolchain has different instructions and some toolchains are pretty hard to update. I've been installing my own to override those. I wanted to get this minimal page out for the Ubuntu deprecation. Should I remove the reference for now?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's fine to leave it in, it helps users a head's up/avoid a surprise, even if we don't have a guide to offer them for updating toolchains.