I wish we could put dynamic things in module imports. I understand why it doesn't work, but it would be so nice to add something like `config.mymodules.moduleA` to the list and not have to think about things...
I wish we could put dynamic things in module imports. I understand why it doesn't work, but it would be so nice to add something like `config.mymodules.moduleA` to the list and not have to think about things...
OK, this seems to be the python that Ansible is using. Being called directly without all the PATH mangling that the .ansible-wrapped script does. Which explains why it does not find the kubernetes module...
(Thanks @darix for the hint)
Running the playbook with -v shows me that it is using a completely different python3 from /nix/store/lhpwdis5hkyljz1d200bj1s6g51ljq9k-python3-3.12.8/bin/python3 which does not have the kubernetes module apparently.
No idea how it picks this up, where it takes that information from and how to fix this...
Hardcoding a nix path, even it is just ~/.nix-profile/bin/python3, is of course not feasible if the code is being used on other machines where this is not guaranteed to exist (as outlined in the answers yesterday).
What am I missing?
Fourth and hopefully last round for the #NixOS #Ansible bubble:
Short recap: Having the kubernetes module in the ansible derivation/package is not enough, it needs to also be in the python3 or python312 derivation/package.
Fun fact:
- `which python3` gives me /home/tux.penguin/.nix-profile/bin/python3
- this links to /nix/store/ipwx571dlhxmdf1n1yd8vgqq5ndjnxba-python3-3.12.8-env/bin/python3
- `which -a python3` only gives me this one python, no other binaries found in the PATH with that name
1. Using /nix/store/ipwx571dlhxmdf1n1yd8vgqq5ndjnxba-python3-3.12.8-env/bin/python3 as ansible_python_interpreter works, the kubernetes module is found
2. Using /home/tux.penguin/.nix-profile/bin/python3 for ansible_python_interpreter works
3. Using "{{ lookup('env','HOME') }}/.nix-profile/bin/python3" for ansible_python_interpreter works
4. Using just python3 DOES NOT work?!?!? What the hell? Even if this is resolved (in the shell at least) to the same python3 binary/link in ~/.nix-profile/bin/python3? What the hell?
For anyone out there using @protonprivacy Mail/Pass on #NixOS, I've packaged the desktop clients from source here, since they only distribute x86_64 versions officially. https://github.com/DuskSystems/nix-proton
@codechimp I love #nixos and I would NEVER run #homeassistant in it.
There's a path of least resistance with home assistant, and I will take that road. Hassos is a tiny bit too opinionated (the supervisor is nice but it can be opaque) but smart people maintain it for one and one purpose only, which is to ruh home assistant. And by golly, I will abide!
@TheTraveller or switch to a modern OS such as #NixOS or #Guix, write only free software and you only ever might have to back-up some data.
@freespiritlinux alles #nixos
3 Notebooks, 1 Desktop, Raspberry-Pi(s), Homeserver, VPS
@freespiritlinux bei mir läuft nixos auf meinem Alltagsgerät.
@demivan Hum interesting thks I honestly just know Talos by name but I would have expected that because #NixOS declarative nature the configuration will be simple, not sure about the moving you talking about.
With #NixOs i can use the GitOps approach tho i think, or at least this is what i am trying to do in the end.
@brodokk I have tried #kubernetes on #NixOS. It is an overkill, IMHO.
I recommend trying out #TalosLinux: https://www.talos.dev/
It is simpler, has less moving parts, and is easier to manage.
For Kubernetes, I recommend setting it up using GitOps approach.
I guess we do #kubernetes now?
I'm just experimenting tho, my current infra on debian with virtual machine and docker compose works fine.
But I do am curious about #kubernetes. Also was searching for an excuse for #nixos that i don't want to use as a desktop, i like the Universal Blue based Fedora, Bazzite and aurora for that.
So anyway if some creatures have any resources on either #kubernetes and #nixos please share because i have no idea what i am doing. (Just kidding but this is an experimentation so i'm learning)
Looks like someone added in support for #nixos #homemanager to the #immich uploader which is great to see! I merged it in so feel free to give it a try all! Should make it easier to get it running now on all the nixos mobile devices.
Packaged the @fragdenstaat project fragdenstaat.de/koalitionstracker for #NixOS, available as services.froide-govplan
Thank y'all for the first day of #Rejekts2025 with great talks and inspiring conversations!
I am excited that I got a spot for the #LightningTalks.
Looking forward to present you #Kubenix a tool leveraging #NixOS modules to declare #K8s workloads fully declarative.
I will also show how its #Helm integration essentially bridges the #CloudNative and #Nix ecosystem effectively, while offering additionally type safety.
See you at 18:15 in the hall #TheNash!
https://discourse.nixos.org/t/yubilock-module-for-waybar/62385
Oooh... graphical waybar Yubikey locking module that can be toggled on & off.... yes please!
dear internet, i have a nixos with an efi-only partition and i want to do luks unlock via ssh from inside initrd. when setting network settings into `boot.initrd.network` and ssh config (with host keys in /boot/efi) into `boot.initrd.network.ssh`, i do not get any action in stage 1 attempting to either bring up the network nor launch SSH. i get the normal systemd-udev prompt for the luks passphrase. any ideas?
#nixos #nix
#NixOS Meetup im @cccda am 2025-04-07T19:00:00.
https://discourse.nixos.org/t/nixos-meetup-darmstadt-2025-04-07/62264