07:35 <elisoli> phoebos pls update neovim package

16:38 <beni> Hello everyone, can someone help me with docker? I'm trying to get a devcontainer to work however the socket doesn't seem to work at all

16:38 <beni> does anyone have experience in this?

19:54 <phoebos> whut

19:54 <phoebos> elisoli

19:55 <phoebos> 0.11.5 is the latest

19:55 <phoebos> ?

21:23 <dery> mhhh, why do we have docker in the repos but not podman?

21:24 <dery> IMO podman is way nicer and arguably... simpler? after turning on the right knobs in the kernel of course

21:24 <dery> there was kiss-containers with it but it was last updated 5 years ago and does not have a license. Trivial code interpretations aside, I decided to repackage them myself from scratch

21:25 <dery> should I submit it to community?

21:26 <dery> it also requires a few packages, but they're all surprisingly tiny: shadow-utils (which depends on libbsd and libdm), passt (it's TINY), and netavark (rust based but offers a pre-made vendor directory, which is nice)

22:02 <dery> no aight the docs say that it might require other stuff

22:03 <dery> I could bundle the various helpers though, they're really only used by it

22:07 <sad_plan> im more curious as to why docker is in community to begin with though

22:08 <dery> well why not really

22:08 <dery> flatpak is

22:08 <dery> and containers are the only sane way to run certain software unfortunately

22:08 <dery> if you have no other choice you either run a vm (which is way slower) or change distro altogether

22:09 <dery> there are also chroots but they bring their own set of problems

22:11 <sad_plan> conty will solve all of your problems with less steps and less dependencies

22:12 <sad_plan> atleast thats my opinion. people can obviously disagree with me on this, and thats fine

22:12 <sad_plan> I still think conty is a better solution here

22:22 <dery> it's nice yea, but I don't personally go crazy with the fact that it's "pre-made". It's basically a huge tarball of stuff that you either like or not

22:22 <dery> while regular containers are way more flexible and configurable

22:23 <dery> even just flatpak

22:27 <sad_plan> you do know that you can make conty use w/e distro you want, right? :P it doesnt have to be arch, and it doesnt have to include all that jazz that it comes with ootb

22:30 <dery> oh that's nice

22:30 <dery> that could be a nice alternative to the random chroots I have lying around

22:30 <dery> but I still feel like it covers different usecases

22:33 <dery> thank you for bringing that up tho, I'm definitely giving it a look

22:44 <sad_plan> its not covered in the official docs though, but if you think about it, its just a squashfs file. so it doesnt have to be arch at all. it can be kiss, it can be oasis, it can be linux from scratch if you want it to :p

22:45 <sad_plan> well yes, it was built for gamers in mind, atleast thats the vibe its given me. I dont recall if its in the docs or not, but with the package list in mind, Id say gaming is its mai purpose :p

23:25 <dery> yea

23:25 <dery> there's a "making your own conty image" section in the readme or smth

23:26 <dery> I think it's covered by that

23:26 <dery> also nice that you can now compile everything required (it bundled bwrap and stuff)

23:39 <sad_plan> there is, but it doesnt cover other distros. not that I think its neccessary, as you can easily just change the script to fetch an alpine tarball instead. I mean its just bash scripts. I do wish it wasnt bash, and instead was just POSIX sh, but for some reason, dev doesnt seem to see it that way 'because conty already has bash' or something along those lines

23:41 <sad_plan> hm, interesting. a new wm using swc https://git.sr.ht/~dlm/hevel

23:41 <sad_plan> its mousedriven