10:52 <travier[m]> nikolaos: You can embed an Ignition config into a FCOS ISO but full applications / containers will likely be too large. I suggest using a container registry on the network to store those

14:30 <hauntedbyribbert> Greetings - I'm working on a somewhat off-label use for CoreOS and was running into issues with configuring autologin. It appears that the builtin user, core, is the only one that the autologin works for. My use case requires autologin for a nonprivileged user, and I'd prefer to build-up on a more minimal OS than to try and disable/cut down from SilverBlue.

14:30 <hauntedbyribbert> I attempted to add a getty service manually, oddly enough it does nothing until the user is signed in, THEN it launches, which isn't the behavior I'm after.

14:55 <walters> hauntedbyribberts: I'm not aware of any reason autologin would only work for `core`

15:19 <hauntedbyribbert> Right? It was confusing me too, but I can't find much on why it wouldn't be working correctly. The account I'm attempting to autologin for does have a password set, but for the more vanilla linux types that doesn't seem to prevent it from functioning. I literally pulled it from here: https://docs.fedoraproject.org/en-US/fedora-coreos/tutorial-autologin/ and changed the username. That's it.

18:15 <hauntedbyribbert> So I just built a new image/ignition and verified.. it's definitely not working as expected. We get a standard login terminal screen and nothing.

18:16 <hauntedbyribbert> Upon further inspection.. it appears it's trying to call /usr/bin/agetty, which doesn't exist and therefore the service fails.

18:16 <hauntedbyribbert> modifying /etc/systemd/system/getty@tty1.service.d/override.conf to point to /usr/sbin/agetty fixes it.