Replies: 0 comments 1 reply
-
I think this should be documented as part of a general bootc / image-mode / bootable container workflow guide, somewhere where people can find general guidelines for how to build base images for different platforms. There are some repositories with examples and downstream docs from the distributions (Fedora, RHEL). I generally agree though that we should link to those guides from here and perhaps mention that these guidelines exist wherever we mention supported image types and cloud platforms. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
First want to start off saying this is absolutely awesome! I love being able to generate images for all platforms 100% locally, and combining it with the Bootc concept just works great.
I would like to ask for some clarification in the docs about recommended packages for AWS images (or vendor-specific images in general). Upstream Fedora have made it clear they do not wish to ship cloud-specific packages in CoreOS (and their reasoning is completely understandable), but end-users who wish to deploy these Bootc images to the cloud would prefer to have the convenience packages installed on the images.
I realise it's not something that can or should be added in the osbuild project since they must be added during the OCI build, but it would be great if you could advise on some packages that are nice to have in order to provide a better experience depending on where you are deploying.
For example the docs could detail:
spice-vdagent
amazon-ssm-agent
open-vm-tools
It's not adding any functionality to BIB or OSBuild, but just clarifying to the consumers of the product which packages could be included in the image before being deployed.
Beta Was this translation helpful? Give feedback.
All reactions