3 ms·
My problem with respins and derivatives like this is, they're usually only backed by one developer, and when that developer gets bored with the project, or gets
by phendrenad2 3y ago
My problem with respins and derivatives like this is, they're usually only backed by one developer, and when that developer gets bored with the project, or gets too busy to keep up with bugfixes and patches, everyone has to abandon it and go back to the base distro. They'd be better off just tweaking silverblue themselves at the end of the day.
- doubled112 3y agoI feel exactly the same way. I use plain old Debian now, but used to love some of the Debian based distros. CrunchBang springs to mind. I tend to stick pretty close to defaults these days, so some scripts and Ansible playbooks configure everything on all of my machines with not a lot of maintenance or future worries.
- hk1337 3y agoI like Debian for servers but prefer fedora for a workstation. Maybe I’m weird.
- doubled112 3y agoNot at all, Fedora Workstation is a pretty decent desktop. I run Debian on all of my server stuff at home too. It's not a perfect desktop, but the consistency between machines is something I appreciate. I use it as my stable base while running most applications from Flatpaks. They're up to date but the OS itself never surprises me.
- hk1337 3y agoYeah, I like Amazon Linux for servers too but not Fedora but you can only use that on AWS
- jcastro 3y ago(Co maintainer here) Yeah this why don't call it a distro. It's just your scripts/ansible playbooks and then github runs "podman build" regularly and spits out an image at the end. At the end of the day it's just running a build step in CI so that your machines just end up with the final image instead of running the playbook/script on each one. Hope that helps!
- SirGiggles 3y agoThis is a tangent, but do you have a resource/link to where the base image is defined? For example I saw that in your blog [1] you used the base on line 1 `FROM ghcr.io/cgwalters/fedora-silverblue:37`. I was wondering where I could find the Containerfile for that, my Google-fu and searching through the Fedora pages are failing me [1] https://www.ypsidanger.com/building-your-own-fedora-silverblue-image/ https://www.ypsidanger.com/building-your-own-fedora-silverbl...
- jcastro 3y agoNot a tangent at all! https://gitlab.com/fedora/ostree/ci-test/ https://gitlab.com/fedora/ostree/ci-test/ is the current location of the composed images we derive from. That's what ends up on quay.io/fedora-ostree-desktops/ which is what we use to make our base images. Fedora is in the middle of a transition to make more official images on quay.io/fedora, I'm sorry I don't have the info offhand, it's probably in here somewhere: https://discussion.fedoraproject.org/tag/silverblue/l/top?period=monthly https://discussion.fedoraproject.org/tag/silverblue/l/top?pe...
- SirGiggles 3y agoThanks for the reply. On the note of quay.io, is there a function on the website to see the Containerfile that created the artifact? I recall digging around in the past but couldn't really find a link to the source Containerfile.
- bigpod 3y agoTotally agreed one man distros might not get maintained after release or two but: Behind Bluefin is a project called Universal blue which is a whole bunch of people with many interests, but biggest one being DevOps, devOps combined with its "immutable", image-based nature which should make maintenance of distro lot easier then normal