!VhzbGHamdfMiGxpXyg:robins.wtf

NixOS LXC

33 Members
lxc, lxd, incus discussions related to NixOS14 Servers

Load older messages


SenderMessageTime
29 Feb 2024
@hexa:lossy.networkhexawow stgraber is really working on integrations everywhere 😄 15:15:01
@hexa:lossy.networkhexa * wow stgraber is really working on integrations with everything 😄 15:15:07
@adam:robins.wtfadamcstephenshe gets to set his own priorities now instead of his employer's :)15:34:15
4 Mar 2024
@aanderse:nixos.devaandersehey team I've been hacking on a little script recently that I've found useful i thought this might be a good place to get some feedback on it as i think a few people here probably use similar technologies it's kinda like terranix + colmena = nixops if anyone wanted to take a look and give some feedback, good or bad, i would appreciate it: https://github.com/aanderse/teraflops of note: specifically there is a lxd backend but that's pretty trivial to include incus as well and something that is on my list01:07:08
5 Mar 2024
@adam:robins.wtfadamcstephenslinuxcontainers borked their DNSSEC, so images.linuxcontainers.org is failing to resolve13:31:58
@hexa:lossy.networkhexa
;; AUTHORITY SECTION:
linuxcontainers.org.	3600	IN	NS	ns1.stgraber.org.
linuxcontainers.org.	3600	IN	NS	ns2.stgraber.org.
13:34:26
@hexa:lossy.networkhexa"linuxcontainers" 😄 13:34:32
@adam:robins.wtfadamcstephensright.13:36:16
@adam:robins.wtfadamcstephensmostly stgraber13:36:27
@adam:robins.wtfadamcstephenshttps://bgp.tools/as/39976013:37:16
@adam:robins.wtfadamcstephensserious about running his own infra13:38:14
@hexa:lossy.networkhexalooks like a failed KSK rollover for stgraber.org and linuxcontainers.org13:38:22
@hexa:lossy.networkhexalooks like he noticed it just now13:43:16
@adam:robins.wtfadamcstephensafter you pinged him, yes :)13:46:25
@hexa:lossy.networkhexa😛13:46:52
9 Mar 2024
@adam:robins.wtfadamcstephensbah, i didn't think enough when refactoring to add lts support to incus and broke overriding 🤦‍♂️16:13:36
@adam:robins.wtfadamcstephens

the three solution i'm seeing are:

  1. move the unwrapped back to its own package
  2. eliminate the wrapper and move the wrapping back into the main package
  3. move the wrapper code into the module
16:14:20
@adam:robins.wtfadamcstephensi started doing #3, but do i want to lose the ability to run this outside systemd if that ever comes to fruition?16:17:06
@adam:robins.wtfadamcstephensmaybe i'm just overthinking potential systemd alternatives16:18:28
@hexa:lossy.networkhexayeah, people have annoyed me with "needs to run w/o the nixos module" alot of times16:20:33
@hexa:lossy.networkhexain which case they should start start maintaining that part16:20:46
@adam:robins.wtfadamcstephensi don't like #2 because coupling a complex wrapper with the package feels wasteful to me16:21:43
@hexa:lossy.networkhexacase in point: matrix-synapse-unwrapped16:22:03
@adam:robins.wtfadamcstephensok, i'll finish up #3. if a systemd alternative ever comes, i can rethink this again then :)16:22:40
@adam:robins.wtfadamcstephensreally this only applies to incusd anyway. there's only one extra package for the client, which is spice for gui consoles16:24:06
@adam:robins.wtfadamcstephens thanks for your input hexa 16:24:24
@hexa:lossy.networkhexayw16:24:32
@adam:robins.wtfadamcstephensbuilding go packages is so refreshing compares to rust :)17:05:46
10 Mar 2024
@adam:robins.wtfadamcstephens mkg20001 if you update the UI package will you make it a full package instead of overriding the lxd one?  17:42:01
@mkg20001:mkg20001.iomkg20001
In reply to @adam:robins.wtf
mkg20001 if you update the UI package will you make it a full package instead of overriding the lxd one? 
why? is there any issue with the override?
18:15:56

Show newer messages


Back to Room ListRoom Version: 10