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

[RFE] Use systemd-repart and dm-verity #4

Open
pothos opened this issue Oct 10, 2022 · 2 comments · May be fixed by #24
Open

[RFE] Use systemd-repart and dm-verity #4

pothos opened this issue Oct 10, 2022 · 2 comments · May be fixed by #24
Labels
kind/feature A feature request.

Comments

@pothos
Copy link
Member

pothos commented Oct 10, 2022

Current situation

We build plain squashfs images

Impact

We don't benefit from dm-verity protection

Ideal future situation

Use systemd-repart to create dm-verity images

@pothos pothos added the kind/feature A feature request. label Oct 10, 2022
@pothos pothos linked a pull request Sep 6, 2023 that will close this issue
@septatrix
Copy link

I have recently come to use mkosi for use-cases like this as it allows easy configuration and supports many neat features such as systemd-repart, automatic dm-verity (including root hash, signature and such), automatic generation of the extension-release file and such.

@gdonval
Copy link

gdonval commented Sep 2, 2024

For what it's worth, cons: mkosi does not support Gentoo as a target, it's not neatly packaged and it breaks fairly often (being "hacked together" mostly with systemd's interactive testing in mind).

Don't get me wrong: it's a neat tool that, in theory, would remove most friction when it comes to producing systexts/portableexts but those cons make it very hard to really rely on it in production (IMHO ofc).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature A feature request.
Projects
Development

Successfully merging a pull request may close this issue.

3 participants