I really don't get the point of setting up a declarative system for one deployment
I really don't get the point of setting up a declarative system for one deployment
CFor a bunch of systems it's extremely cool, but for desktop?
SAlso, latest drama pushed me further away. Now I'm using a version of Fedora Atomic, because it seems I love having to use workarounds to do basic stuff, like setting a QMK dev environment
Hthere's no practical merit on the desktop aside from being able to reconstruct the system if you do something incredibly stupid
Heg dd'ing your main drive
Hbut yeah honestly the only truly practical applications is either deploying a fuckton of machines without manual work, or CI style stuff
CWhy don't people just install Gentoo instead? lol
Hbecause gentoo has all of the issues of regular distros with none of the benefits?
Hxd
CBut if the practical benefit is bragging rights
SI used to run Gentoo, many, many years ago. It seems it's a trend of me really liking using gimmicky stuff that has little to no benefit
KOh talking about declarative stuff, I trashed my distrobox the other day trying to install and get Docker working for Microsoft thing and ended learning about the .ini stuff
After a night fighting it because I was already dumbed down of working for a bunch of straight hours at that point, there's one thing I couldn't figure out...
The Distrobox is using Fedora and I can't add the Microsoft .repo on the ini file
After a night fighting it because I was already dumbed down of working for a bunch of straight hours at that point, there's one thing I couldn't figure out...
The Distrobox is using Fedora and I can't add the Microsoft .repo on the ini file
SLeaving the PC running all night to compile a browser is really fun
Hi mean if that's the goal then sure
KSame here hah
SYeah, I was wondering here, I think I'll need to run Docker, and was thinking on how to best approach it. So the better solution is to use distrobox and install docker inside it, right?
ZNixos manages to solve an issue that many distros have. And that is dependency hell
SA container inside a container
SContainerception
Jpeople have been doing this for years, for some reason new nix users think that you have to use nix to do this, which is weird.
Kiirc I set up QMK without any problem
JMy desktop comes up the exact way I want on install every time, I'm not using nix.
KI don't know I ended up layering it with ostree 
Htrue but like
i don't like ansible and other stuff lmao
i don't like ansible and other stuff lmao
KJust in a distrobox, I had no problem
Hmostly because i can't even install it here without hoops
Jdon't like it either, that's why we built on bash and python instead of ansible, if ublue was built on ansible then that'd be cool, but no one would contribute
SI tried installing and setting it up through pip but got rekt by the dependencies, probably because it can´t deal with ostree shenanigans
KI couldn't get it working through containerception lol
Jif you're doing a bunch of that stuff it might make sense to just make your own container image
KThe issue was the systemd service having an error
KAh, makes sense than
ZSystemd?
CI read contraception, had to double take
KI think I set it up through pip as well, just, through an F40 distrobox
SSo I was thinking of using the docker thing, but then I don´t have docker. I´d need to either layer it (which is not recommended) or do some weird stuff like containerception
ZI think I had the same issue, had to add the
--additional-packages systemdKOh you don't have it set up yet, in that case, distrobox works
Heh, preferences 
im not doing anything serious anyway
im not doing anything serious anyway
JI always just steal what someone else is doing
Hnix is pretty much a hobby with a possibility of it being a marketable skill for me
SAs I mentioned, it's the manly urge of using weird distros that require obtuse workarounds to do things that you can do with a single command in other distros
SFor little to no benefit
KYeah I'm using the conf files instead which worked if I added root I think
The thing was VSCode not being able to communicate with Docker
The thing was VSCode not being able to communicate with Docker
Hlike it's just fun doing weird things
KYeah it's just fun and you have the pretext of it being more stable hah
SHonestly, it doesn't really work even for bragging rights. People just call me a nerd and move on. No one is impressed that I spent 20+ hours setting up my system
ZGitHub
Linux virtual machines, with a focus on running containers - lima-vm/lima
KAbout that yeah I figured it is probably the way to go in my case, unless I missed something with the Distrobox
ZAnd can be installed with brew
Tdocker-machine also works for that doesnt it?
