-
Notifications
You must be signed in to change notification settings - Fork 18
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
Share examples to help onboard new users #864
Comments
Some follow up issues after #895 but unsure if it's in the scope?
What else should we have? |
I was just trying to build a custom image this evening and have some ideas! The httpd, tailscale, and other httpd examples are pretty "appdeveloper cloud person" oriented. I was thinking from the other direction, highlighting the operating system since that's a killer feature in bootc. I was thinking something like grouping them into use cases:
And then you FROM the usual barebones image, but then recommend some groups to install that match those use cases, and then leave a little boilerplate for "Add your packages here!". Then these examples automatically become useful to homelabbers and enthusiasts. And then if appropriate add images from orgs in ADOPTERS.md, and maybe having those orgs in the examples directory will incentivize them to submit their logo. 😄 |
That would be awesome and would love to add that. Only problem is that we have to make sure these are hosted somewhere as we are pulling them :) If it's a maintained quay / docker hub location, I totally don't mind adding some from the community! Would be awesome having graphical OS's as well (would love bazzite to be bootc-compatible one day...) |
Epic domain
Make it as easy as possible for users to create bootable containers, starting with a curated list of examples or "recipes". For instance, examples for building images for databases, a virt host, etc.
There is already a repository that we may be able to leverage for this: https://gitlab.com/fedora/bootc/examples
Additional context
No response
The text was updated successfully, but these errors were encountered: