Per discussion, "from scratch" is more descriptive of what's
going on. Every bootc base image is custom in a sense.
Also, link the from scratch flow from the "don't run dnf -y update"
section, as folks doing that probably want scratch builds
instead.
Signed-off-by: Colin Walters <walters@verbum.org>
Certain things do not work in a container-build environment that are
worth mentioning. Overall, I expect this section to evolve over time
and maybe turn into something more formal.
Signed-off-by: Valentin Rothberg <vrothberg@redhat.com>
Document a trick to free up space on the runner to increase the chances
of not running into a space issue.
Signed-off-by: Valentin Rothberg <vrothberg@redhat.com>
The referened issue has been fixed in the meantime, so don't bother
users with it. /etc/alternatives just works today.
Signed-off-by: Valentin Rothberg <vrothberg@redhat.com>
Based on some lessons I've learned this week, I figured to share them in
form of best practices in the docs. I believe those will help users
during the on-boarding process and can be further improved and extended.
Signed-off-by: Valentin Rothberg <vrothberg@redhat.com>
I want to be explicit on mentioning Dockerfiles as a way to customize
base bootc images. It is somehow implied but not explicitly mentioned
until the http example.
Signed-off-by: Valentin Rothberg <vrothberg@redhat.com>
Since this repo is still in flux, it didn't seem worth trying to
meticulously split out smaller commits.
Briefly:
- fix/improve the rendering of various boxes/paragraphs/code blocks
- fix some links
- use Fedora for one of the httpd example; add fix required for that
- define the `caddy.container` file before the `Containerfile` since the
latter references the former
- remove some repetitions
- use codestyle for the quay.io/ references
- reference the minimal image built from the same official repo instead
of the experimental one for consistency
