20ff0865c7
Followup to 9a0acd7249
Basically our composefs enablement flag has long had a tension between
trying to do two things:
- Enable generating the composefs blob (at deployment time)
- Enable at runtime in prepare-root
And we've hit issues in "ratcheting" enabling composefs
across upgrades because of this.
This change builds on the previous one, and now it's really
simple to talk about:
- If composefs is enabled at build time, we *always*
generate a composefs blob at deplyment time
- Configuring the prepare-root config now mostly
only affects the runtime state.
There is one detail though: in order to handle the
verity requirement at deploy time, we do still parse
the config then.
But for the basic "is composefs enabled at all at runtime"
that is now fully keyed off the config, not the build time
or (worse) whether the deployment happened to have a composefs
blob.
For users who want composefs on, they need to do so in the base
image configuration.
Signed-off-by: Colin Walters <walters@verbum.org>
This documentation is written in Jekyll format to be published on GitHub Pages. The rendered HTML will be automatically built and published, but you can also use Jekyll locally to test changes.
First you need to install Ruby and
RubyGems to get Jekyll and the other gem
dependencies. This is easiest using the distro's packages. On RedHat
systems this is rubygems and on Debian systems this is
ruby-rubygems.
Next Bundler is needed to install the gems using
the provided Gemfile. You can do this by running gem install bundler or using distro packages. On RedHat systems this is
rubygem-bundler and on Debian systems this is ruby-bundler.
Now you can prepare the Jekyll environment. Change to this directory and run:
bundle config set --local path vendor/bundle
bundle install
Finally, run the prep-docs.sh script and then render and serve the
site locally with Jekyll:
./prep-docs.sh
bundle exec jekyll serve