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

deploy: Honor prepare-root.conf at deploy time for composefs #3165

Merged
merged 4 commits into from
Feb 9, 2024

Commits on Feb 8, 2024

  1. lib: Move parsing of composefs config into otcore

    So it can be shared with the deployment path.  Prep for dropping
    `ex-integrity.composefs`.
    cgwalters committed Feb 8, 2024
    Configuration menu
    Copy the full SHA
    7d9fa8e View commit details
    Browse the repository at this point in the history

Commits on Feb 9, 2024

  1. prepare-root: Fix crash if no keys were found

    Handle a NULL pointer.
    cgwalters committed Feb 9, 2024
    Configuration menu
    Copy the full SHA
    95f4bb6 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    d8f03c6 View commit details
    Browse the repository at this point in the history
  3. deploy: Honor prepare-root.conf at deploy time

    I want to try to get away from the "repository global" configuration
    in the repo config.
    
    A major problem is that there's not an obvious way to configure
    it as part of an ostree commit/container build - it needs
    to be managed "out of band".
    
    With this change, we parse the `usr/lib/ostree/prepare-root.conf`
    in the deployment root, and if composefs is enabled there,
    then we honor it.
    
    We do still honor `ex-integrity.composefs` but that I think
    we can schedule to remove.
    cgwalters committed Feb 9, 2024
    Configuration menu
    Copy the full SHA
    cae4ceb View commit details
    Browse the repository at this point in the history