doc: introduce advanced bootc#462
Conversation
supakeen
force-pushed
the
doc-bootc-advanced
branch
16 times, most recently
from
d249fde to
2728c8a
Compare
|
Found a small bug while testing out the documentation that we will address: osbuild/images#2228 for now it has a warning that LVM base partition tables don't work with bootc images. |
supakeen
force-pushed
the
doc-bootc-advanced
branch
5 times, most recently
from
af0a08e to
be2a629
Compare
|
Related to this (I think) the osbuild.github.io readme-list should pull the README from https://github.com/osbuild/images/blob/main/data/files/pxetree/README and add it as a new section on bootc-pxe-tar |
supakeen
force-pushed
the
doc-bootc-advanced
branch
from
be2a629 to
bcc0592
Compare
supakeen
force-pushed
the
doc-bootc-advanced
branch
from
bcc0592 to
eb31ea1
Compare
supakeen
force-pushed
the
doc-bootc-advanced
branch
11 times, most recently
from
7b34aba to
9f6cd0f
Compare
|
This PR is stale because it had no activity for the past 30 days. Remove the "Stale" label or add a comment, otherwise this PR will be closed in 7 days. |
|
Not stale. |
supakeen
force-pushed
the
doc-bootc-advanced
branch
from
9f6cd0f to
5a37c21
Compare
Using the newly introduced advanced section move the `Containerfile` for installer setup into it. Also write down a new section of sources of configuration for `image-builder` when converting bootable containers. Signed-off-by: Simon de Vlieger <cmdr@supakeen.com>
supakeen
force-pushed
the
doc-bootc-advanced
branch
from
5a37c21 to
c430891
Compare
|
Going to undraft because it's quite far along and already super useful. I want to do more smaller changes instead of a big bang. The only /real/ thing missing here is the |
|
|
||
| For a `payload_type: filesystem` the `payload` has the following properties: | ||
|
|
||
| - `type` |
There was a problem hiding this comment.
Missing a description of type here.
|
|
||
|
|
||
| - `label`, an *optional* `string` that contains the filesystem label. | ||
| - `fstab_options` |
| mountpoint: "/var" | ||
| ``` | ||
|
|
||
| *To use `btrfs` your container must set its configured root filesystem to `btrfs`, or it must be passed when `image-builder` is called.* |
There was a problem hiding this comment.
'must be passed' should say how (using --bootc-default-fs is the only way, right?)
brlane-rht
left a comment
brlane-rht
left a comment
There was a problem hiding this comment.
Looks pretty good. A few minor missing things, but no reason to block if you want to fix them later.
5 participants
Using the newly introduced advanced section move the
Containerfilefor installer setup into it. Also documentdisk.yamlandiso.yaml.The
disk.yamlis our general partitioning format in the YAML definitions so when we start officially exposing/documenting that the section can move and we can refer to it.