Is there any way to edit the kickstart file created in the "Release-ISO" workflow
Is there any way to edit the kickstart file created in the "Release-ISO" workflow
EFork isogenerator, edit the ks here, build it using the action, update the release-please workflow to use your fork:
https://github.com/ublue-os/isogenerator/blob/main/installer/kickstart/ublue-os.ks
https://github.com/ublue-os/isogenerator/blob/main/installer/kickstart/ublue-os.ks
Xdiscussed this in #
custom-image-support and this is what i think alex ended up doing / thinking of doing
custom-image-support and this is what i think alex ended up doing / thinking of doing
AIndeed it is, I wasn't sure of the right thred to post the question into, sorry. The problem I see is that I will likely end up posting the WiFi password and SSID into a public fork. (Though that's likely a problem either way)
AIt may be that editing the ISO post download to inject the Kickstart for a Root Password and WiFi details is the best way to go, without storing those details in the cloud. Maybe reworking this to prompt the user for input could be the safest way to go. https://github.com/alextrical/Fedora-Kinonite-Fablab-Kickstart
GitHub
Fedora Kinonite Fablab Kickstart and Configuration - GitHub - alextrical/Fedora-Kinonite-Fablab-Kickstart: Fedora Kinonite Fablab Kickstart and Configuration
APutting credentials inside the installer image is a bad idea
AAsking for wifi password after install is basically what gnome/kde already do no?
AIt's for deployment inside a Makerspace, so I'm hoping to minimise effort required to restore a working system. The problem is that it asks for the WiFi details after installing, but if the user doesn't enter them in Anaconda the install fails to fetch the built os, and as a result can't install the OS
AOh you’re trying to install the OS using wifi
Acreate a temporary ssid/password and hardcode it in
ADestroy after deployment
AOut of curiosity, Is there a way you would recommend setting up both a Admin account and a Kiosk (public user) account?
AThat could work, they now have a Draytek router which allows up to 4 SSID's and we could set the last one to be enabled when re-provisioning.
Though is there really that much danger having the Kickstart configured on a pendrive, when it's kept securely in the owners office drawer?
Though is there really that much danger having the Kickstart configured on a pendrive, when it's kept securely in the owners office drawer?
AI suppose I'm aiming to do the equivalent of as close as possible to a preconfigured OS deployment. Back in the XP days, Sysprep was amazing for getting a monoculture of PC's setup identically with minimal input of the technicians. I'm hoping to make something as elegant as that for the Makerspace, Ideally, insert a USB key, reboot, select HDD to install to and select install. Once done ideally have WiFi, Admin and Kiosk user accounts created, all the software installed and configured ready to go, including connection to the central owncloud file share
JI think @Caleb Woodbine wants something similar, maybe you can compare notes
JOnce the tooling lands the oci support that shouldn't be a problem. I was doing that at an edu with the full automation, automated pxe install, zero config other than turning the machine on. That was 2006, so it'll be at least that good, hahah.
AActually it may be possible to do a PXE install, as I'm going to be setting up a local storage server in some form. Though WiFi only could be the killer for that idea
AGood shout, thank you for the heads up. Hopefully we can collaborate
Jthe stick will come first, this is the tooling we're going to be using: https://github.com/osbuild/osbuild
Jupstream is in the middle of adding a bunch of the features/fixes needed
AYeah I would say so, it’s just a password laying down somewhere in plaintext
AAnyway if you plan to have recurring provisioning you should definitely setup a separate network for that process
ASeparate ssid/vlan isolated from production traffic
AThe password is encrypted in the Kickstart, though I'm not sure how hard it would be to crack it
AThe key would be with the encrypted password
AUnless you require manual intervention to decrypt it
AAh, good point
AIt's trying to find the right amount of work to secure a setup of 10 machines in a small Makerspace. Having a dedicated network is probably a bit overkill for the workshop setup 
A10 machines you could also just use the usb approach
AAnd then destroy it right after
AIf it’s 1 usb
AHmm, yeah erasing the USB is probably the best way to go then. I will get a script to inject the Kickstart and prompt the admin to enter the Root password and WiFi credentials
AOut of curiosity is there a central account database fedora can use similar to Active directory to synchronise user accounts (i.e. one place to change an admin password instead of per machine)
AHec, even something like windows live login would be awesome
AFreeIPA
AWill add that to the list of reading materials, thank you 
BActive directory, freeipa, so on there are few options
AIf I can enroll an admin account to FreeIPA running on a Docker based server, with minimal human interaction for the workstation OS install, that's the route that's probably best. I'm hoping a single point to change the Admin/Root password across all machines would be pretty useful
AI'm familiar enough with setting up a Windows domain, just doing something similar on Linux is rather new to me 
Just want to fully get rid of M$ rubbish from my life and the communities I'm helping out, where possible
Just want to fully get rid of M$ rubbish from my life and the communities I'm helping out, where possible
LHowdy! I've got some public discussion over here
https://universal-blue.discourse.group/t/building-a-bootable-qcow2-virtual-disk-image-from-an-oci-ostree-image/67
https://universal-blue.discourse.group/t/building-a-bootable-qcow2-virtual-disk-image-from-an-oci-ostree-image/67
Universal Blue
Hi folks 
I’m with ii.nz 
and am trying to build bootable USB drives for things like education for classes and shared team development environments. Recently I came across GitHub - osbuild/osbuild-deploy-container, where a qcow2 image can be built, given an OCI OSTree image (i.e: a Universal Blue image). I built a qcow2 image for my u imag...
I’m with ii.nz and am trying to build bootable USB drives for things like education for classes and shared team development environments. Recently I came across GitHub - osbuild/osbuild-deploy-container, where a qcow2 image can be built, given an OCI OSTree image (i.e: a Universal Blue image). I built a qcow2 image for my u imag...
AAwesome, Is the intended application you are aiming to achieve something similar to a LiveBoot (On par with Windows to Go?)
ACan anyone advise how to apply a RPM file hosted in GitHub into the Recipe.yml
I'm trying to get "STL Thumb" intergrated into the system.
I'm trying to get "STL Thumb" intergrated into the system.
ATo answer my own question, Looking at the Bling for devpod shows how to use rpm-ostree to install a RPM file directly from a URL
ASo. It's installed, as it shows as a conflict if I try to install from the updated OS image, woop. However I cannot get the command to run from terminal, presumably wherever it's installed to isn't the correct location.
The counter problem is it's also an application I've had to compile as a rpm too, so that is also a likely place for the issue. Why do rabbit holes always go so deep in projects
The counter problem is it's also an application I've had to compile as a rpm too, so that is also a likely place for the issue. Why do rabbit holes always go so deep in projects
LI think so!
Not completely familiar with Windows to Go but it sounds familiar.
Pretty much an install preloaded with a default user and default software for a specific purpose, being an education resource
Not completely familiar with Windows to Go but it sounds familiar.
Pretty much an install preloaded with a default user and default software for a specific purpose, being an education resource
AI would be happy to collaborate, it could be useful for some makerspaces out there wanting to allow users to use their own laptops with a pre-loaded system too.
Making an atomic Live USB boot device with persistent storage should be pretty useful to some people ^_^
Making an atomic Live USB boot device with persistent storage should be pretty useful to some people ^_^
LThat sounds great!
I'm keeping track of progress here
https://github.com/ii/uedu/issues/1 and the discourse as linked before.
Also talking to folks in the image-builder channel of the Fedora project Matrix
https://matrix.to/#/#image-builder:fedoraproject.org
Some of which are here too I think
I'm keeping track of progress here
https://github.com/ii/uedu/issues/1 and the discourse as linked before.
Also talking to folks in the image-builder channel of the Fedora project Matrix
https://matrix.to/#/#image-builder:fedoraproject.org
Some of which are here too I think
GitHub
build a bootable Fedora/OSTree based image include the following software Scratch Sonic Pi Minecraft Forge an IDE? include a PDF or webpage for course instructions webserver? current issues include...
You're invited to talk on Matrix. If you don't already have a client this link will help you pick one, and join the conversation. If you already have one, this link will help you join the conversation
Aat the moment im going down a rabbit hole trying to get a STL thumbnail generator working. (good news, it works for Fedora KDE Workstation, but not Kinoite)
J@bsherman tomorrow is 37 day but if we wanna start nuking from orbit asap that wouldn't hurt either
J(It's the only way to be sure)
J@beekabop I tried the new release-please action in kera and it broke with the major upgrade
