| 10 Mar 2024 |
 hexa | anyway, one weird thing I imagined is zfs send/recv style migrations | 19:19:26 |
| hexa | I think proxmox could do that | 19:19:36 |
| hexa | and it might be appealing since zfs has alot less moving parts than ceph | 19:19:47 |
 adamcstephens | at least for non-clustered incus, i think it does use zfs send/recv for migrations | 19:34:21 |
| adamcstephens | it may for clustered too when it's not a shared volume | 19:34:42 |
| adamcstephens | * it may for clustered too when it's not a shared pool | 19:34:45 |
|  cmspam joined the room. | 19:34:51 |
| cmspam | Hello, everyone. | 19:40:11 |
 mkg20001 | In reply to @adam:robins.wtf
I’m also still hoping to deprecate lxd. I’ve just been waiting for incus LTS i'll make it seperate packages then | 19:42:03 |
| mkg20001 | https://github.com/NixOS/nixpkgs/pull/294802 | 19:50:36 |
| cmspam | Redacted or Malformed Event | 20:06:39 |
| cmspam | Redacted or Malformed Event | 20:11:26 |
| cmspam | I figured it out. Here is the pull request for the new test. | 20:36:35 |
| cmspam | https://github.com/NixOS/nixpkgs/pull/294819 | 20:36:36 |
| adamcstephens | In reply to @cmspam:matrix.org
https://github.com/NixOS/nixpkgs/pull/294819 I was expecting you to add that to your other PR. :) | 21:34:42 |
| cmspam | adamcstephens 🐝: Yes, it would have made much more sense to put it there :D
The code review you put requesting changes to requires, the changes have been fulfilled. Have I submitted that correctly and it's back to you, or I need to do something further to indicate it's implemented in github? | 22:17:34 |
| adamcstephens | In reply to @cmspam:matrix.org
adamcstephens 🐝: Yes, it would have made much more sense to put it there :D
The code review you put requesting changes to requires, the changes have been fulfilled. Have I submitted that correctly and it's back to you, or I need to do something further to indicate it's implemented in github? Yeah it’s back to me. I’ll take a look, probably this evening, and get back to you | 22:44:39 |
| 14 Mar 2024 |
|  NixOS Moderation Botchanged room power levels. | 18:44:26 |
| 18 Mar 2024 |
| mkg20001 | Should we add networking.firewall.trustedInterfaces = [ "incusbr*" ]; as part of the default incus configuration? Or is there a better solution? | 13:45:05 |
| mkg20001 | people are running into this quite often: https://discuss.linuxcontainers.org/t/incus-on-nixos-with-tailscale-on-the-side-no-internet-access-for-the-containers/19385/2 | 13:45:43 |
| adamcstephens | unfortunately they could name the bridge whatever they want | 13:48:08 |
| adamcstephens | incusbr0 is a convention (following on lxdbr0) but you could just as easily name the network/bridge myfavbr0 | 13:48:49 |
| adamcstephens | i'm hoping to start building out a wiki page once Wiki 2 is official | 13:50:47 |
| adamcstephens | maybe this advice could live there? | 13:50:55 |
| adamcstephens | * i'm hoping to start building out a wiki page once Wiki 2 is live | 13:51:08 |
| mkg20001 | wiki 2? | 13:51:38 |
| adamcstephens | https://discourse.nixos.org/t/official-nixos-wiki/38715 | 13:52:00 |
| adamcstephens | or whatever we want to call it :) | 13:52:15 |
| mkg20001 | i'm thinking if there is a good way to make incus work by default | 13:53:23 |
| mkg20001 | I've seen your paste aswell with the nftables rules, but I feel like the real fix is just adding a hook to lxd that it adds the trusted interface dynamically, as otherwise we end up trying to allow everything lxd wants, while lxd may or may not require something extra depending on it's settings... we could use named sets to achive the trusted interface change dynamically and temporarly | 13:53:50 |
