<zimbatm>
^ let me know if it's the wrong place for the edit
<makefu>
i think it is fine, it is a wiki after all :)
timokau[m] has joined #nixos-wiki
hl has joined #nixos-wiki
olejorgenb[m] has joined #nixos-wiki
florianjacob has joined #nixos-wiki
jtojnar has quit [Read error: Connection reset by peer]
jtojnar has joined #nixos-wiki
<samueldr>
by the power of OP?
<samueldr>
ah, operator
<makefu>
yep
<samueldr>
I wondered how it was related to the page I wrote
<makefu>
haha, no the kick was after the page
<makefu>
you are using proxmox?
<samueldr>
trying it, nixos containers don't work exactly how I like, and I still need to, sometimes, run non-nixos containers
<samueldr>
while also having qemu virtualization
<samueldr>
for right now, I have to say it's not bad, though it has some rough edges
<samueldr>
ideally, I would have liked to use an interface for libvirt under a nixos host, but I didn't find anything that worked well enough (for web-based interfaces) and had issues with LXC+libvirt on nixos
<samueldr>
though the qemu bits worked fine
<samueldr>
oh, and templates, it was a chore to always start from scratch
<samueldr>
(though maybe some of the issues are because I didn't use it the right way?)
<makefu>
actually i've never heard of the move towards containers in proxmox. i always thought of it as a vmware-*light*. but it is quite cool to see them moving into the future
<Mic92_>
are container the future or VMs? Or Container in VMs?
<samueldr>
the future is running your code on someone else's computer :D
<samueldr>
though, I have no strong opinions for or against *in general*
<samueldr>
both have their places
<samueldr>
and that's for "system containers", not docker-like containers
<fadenb>
Mic92_: Yes
<fadenb>
;)
<fadenb>
From what I gather at customers (usually large and very very enterprise style it) containers are coming but it will take years
<fadenb>
At one customer they are currently training staff on docker but at the same time security forbids the use of docker :P
<samueldr>
hah
ixxie has quit [Ping timeout: 255 seconds]
<joepie91>
Mic92_: they solve different problems really
<Mic92_>
joepie91: yeah, most people are using containers as a substitition for their otherwise bad package manager.
<joepie91>
that, too :)
<Mic92_>
they don't even enable namespaces from time to time
<joepie91>
Mic92_: I've found that a shockingly small amount of people understands the distinction between dependency isolation and runtime isolation...
<joepie91>
including people building package managers
<joepie91>
(as in, some of them don't understand this distinction)
<joepie91>
with the result that people try to solve dependency isolation by applying runtime isolation
<joepie91>
but runtime isolation is much more expensive to solve...
<joepie91>
actually, let's not get too deep into a rant :)
<joepie91>
I'm in a slightly sour mood given that I've just had a dependency maintainer yell at me over a perfectly valid security advisory
<joepie91>
and wrongly claiming that there 'has never been a vulnerability'