GHA ci with fsverity #389
Labels
enhancement
New feature or request
Comments
I hit this same issue in composefs_experiments and solved it the same way (loopback-mounted verity-enabled ext4). I specifically wanted to avoid the tune2fs approach because it hardcodes the name of the root device which could maybe change. |
|
Sure, just replace |
|
That's something I could get behind :) |
allisonkarlitskaya
added a commit
to containers/composefs-rs
that referenced
this issue
Oct 29, 2024
...instead of using an extra loopback partition. Suggested by Colin in containers/composefs#389.
allisonkarlitskaya
added a commit
to containers/composefs-rs
that referenced
this issue
Oct 29, 2024
...instead of using an extra loopback partition. Suggested by Colin in containers/composefs#389.
allisonkarlitskaya
added a commit
to containers/composefs-rs
that referenced
this issue
Oct 29, 2024
...instead of using an extra loopback partition. Suggested by Colin in containers/composefs#389.
|
Works great. Just did this in containers/composefs-rs#19 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Previously I added a hacky loopback mounted ext4, but in some quick testing I noticed that testing via the default GHA runner just needs
tune2fs -O verity /dev/sda1for reference.We should be able to rework some of our tests to use this.
The text was updated successfully, but these errors were encountered: