Skip to content
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

Update dependency kairos-io/kairos to v3.1.2 #190

Merged
merged 3 commits into from
Aug 31, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 10, 2024

This PR contains the following updates:

Package Update Change
kairos-io/kairos minor v3.0.14 -> v3.1.2

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

kairos-io/kairos (kairos-io/kairos)

v3.1.2

Compare Source

⚠️ The following issues have been resolved, so it is safe to upgrade again:

Kairos user ids change on upgrade, breaking ssh login #​2797
Long duration hang during boot #​2802

What's Changed

Full Changelog: kairos-io/kairos@v3.1.1...v3.1.2

v3.1.1

Compare Source

Upgrade issues

Be advised that there is currently an issue when upgrading from 3.0.x to 3.1.x in which the user ids will change. This will result in any files owned by the user under its /home directory to lose permissions which can lead to not being able to ssh (ssh keys will have a different user id)

We are currently working on a workaround, so you are advised to not upgrade until 3.1.2 is released with a fix for this.

What's Changed

Bug fixes 🐛

Known Issues

  • RPi EFI booting no longer supported on kernels shipped with Ubuntu 24.04+ #​2249

Full Changelog: kairos-io/kairos@v3.1.0...v3.1.1

v3.1.0

Compare Source

Upgrade issues

Be advised that there is currently an issue when upgrading from 3.0.x to 3.1.x in which the user ids will change. This will result in any files owned by the user under its /home directory to lose permissions which can lead to not being able to ssh (ssh keys will have a different user id)

We are currently working on a workaround, so you are advised to not upgrade until 3.1.2 is released with a fix for this.

Potential Breaking Changes

By default, Uki artifacts (identified by the -uki suffix) no longer include Linux modules and firmware in the image. Real-world testing has shown that many EFI firmwares are very particular about the size of the EFI image, often refusing to boot if the file exceeds 300-400MB. Given the wide variety of EFI firmware implementations, predicting whether a UKI EFI file will boot on different hardware is challenging.

To enhance compatibility, we decided to slim down the UKI files by removing the largest components: the Linux modules and firmware packages. This results in EFI files around 200-300MB, which are much more likely to boot correctly across various EFI implementations.

However, this change comes with a trade-off. Smaller images, while being more compatible with a wide range of EFI firmwares, may lack comprehensive hardware support because they do not include all the Linux modules and firmware packages. This means that certain hardware components may not function correctly or optimally when using these slimmer UKI images.

On the other hand, larger UKI images, which include all necessary modules and firmware for extensive hardware support, provide better functionality and compatibility with a broad range of hardware. However, these larger images are more likely to encounter boot issues due to EFI firmware limitations, as many EFI implementations refuse to boot files larger than 300-400MB.

We publish -uki artifacts ourselves, which are the slimmed versions, as examples of how to build a slimmer UKI artifact. While these serve as a reference, we recommend always building your own custom images to tailor them to your specific hardware needs. If you need to include those packages for full hardware support, you can create a custom artifact to add them back, as detailed in the Kairos docs.

We recommend keeping your UKI EFI files as small as possible to maximize boot success across different EFI firmware implementations. While smaller images offer better compatibility, they may lack full hardware support. Conversely, larger images, which include all necessary modules and firmware, provide comprehensive hardware support but may fail to boot due to EFI firmware constraints.

Check out how to build your own base images with the Kairos Factory

What's Changed

💿 UKI

🐧

🐛

📖

🔧

New Contributors

Full Changelog: kairos-io/kairos@v3.0.14...v3.1.0


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/kairos-io-kairos-3.x branch from 08381ea to cbd97e7 Compare July 19, 2024 11:23
@renovate renovate bot changed the title Update dependency kairos-io/kairos to v3.1.0 Update dependency kairos-io/kairos to v3.1.1 Jul 19, 2024
@renovate renovate bot force-pushed the renovate/kairos-io-kairos-3.x branch from cbd97e7 to a43591a Compare August 29, 2024 22:52
@renovate renovate bot changed the title Update dependency kairos-io/kairos to v3.1.1 Update dependency kairos-io/kairos to v3.1.2 Aug 29, 2024
Copy link
Contributor Author

renovate bot commented Aug 31, 2024

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@sdwilsh sdwilsh merged commit 6850624 into main Aug 31, 2024
3 of 4 checks passed
@sdwilsh sdwilsh deleted the renovate/kairos-io-kairos-3.x branch August 31, 2024 03:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant