!VhzbGHamdfMiGxpXyg:robins.wtf

NixOS LXC

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

Load older messages


SenderMessageTime
27 May 2024
@adam:robins.wtfadamcstephens yeah, agreed. i figured the sudo exec showed it should work 15:27:18
@adam:robins.wtfadamcstephensnow you have me doubting it :)15:27:27
@hexa:lossy.networkhexasudo is unconstrained root access15:29:08
@hexa:lossy.networkhexa if your incus systemd units don't have hardening (CapabilityBoundingSet in this case), then all is well 15:29:41
@adam:robins.wtfadamcstephensthey don't15:38:27
28 May 2024
@hexa:lossy.networkhexa
# incus launch images:nixos/unstable nixos -c security.secureboot=false
Launching nixos
Error: Failed instance creation: Failed creating instance record: Unknown configuration key: security.secureboot
11:54:50
@hexa:lossy.networkhexaon 6.0.0 🤔11:54:57
@hexa:lossy.networkhexa missing --vm flag in wiki example, fixed 11:57:20
@adam:robins.wtfadamcstephensthanks for fixing13:06:45
@hexa:lossy.networkhexaonline migration with zfs is working fine14:11:58
@hexa:lossy.networkhexaloving the remote cli acccess to the cluster14:12:09
@hexa:lossy.networkhexaa bit annoying that it is stuck with a single node14:14:54
@hexa:lossy.networkhexaimage.png
Download image.png
14:25:02
@hexa:lossy.networkhexathe capitalization is off14:25:12
@adam:robins.wtfadamcstephenshmm, i'm not sure where that comes from14:39:18
@adam:robins.wtfadamcstephens
In reply to @hexa:lossy.network
a bit annoying that it is stuck with a single node
what does this mean?
14:39:26
@hexa:lossy.networkhexa so you can set up your local CLI to use remotes14:41:38
@hexa:lossy.networkhexa * so, you can set up your local CLI to control remote clusters over the HTTP API14:42:51
@hexa:lossy.networkhexa incus config trust add foo prints a token 14:43:06
@hexa:lossy.networkhexa and you can configure that with incus remote add somecluster <token> 14:43:19
@hexa:lossy.networkhexa and then incus remote switch somecluster 14:43:26
@hexa:lossy.networkhexa but this isn't somecluster, it is somehostofsomecluster only 14:43:40
@adam:robins.wtfadamcstephensahh, so the remote isn't cluster aware14:43:56
@hexa:lossy.networkhexayeah14:44:02
@hexa:lossy.networkhexathe keying probably is14:44:04
@hexa:lossy.networkhexabut the CLI isn't smart enough to failover to other cluster members14:44:17
@adam:robins.wtfadamcstephensyeah that's a shame. so you'd have to add all the nodes individually and target them 14:46:16
@hexa:lossy.networkhexaand switch projects as needed 🙂 14:46:26
@adam:robins.wtfadamcstephenswhat kind of environment are you trying to replace?14:48:36
@adam:robins.wtfadamcstephensvmware?14:48:39

Show newer messages


Back to Room ListRoom Version: 10