The 3 hard problems in DevOps engineering are running rm -rf ./ and copy paste mistakes
Remote
ioSyd
@phileas@infosec.exchange
Tech, science, NixOS/DevOps Engineer, anti-discrimination, Internet governance, hacking, workers rights...
Ping me for #FreeLinuxSupport
Drop me a hello if you want to :)
79
Followers
105
Following
14
Posts
Joined December 18, 2022
Stats:
1994/White
Residency:
Vienna/Austria
Pronouns:
they/them!
Work:
GitHub:
GitLab:
Posts
Replying to
@tivasyk@awawa.club
@tivasyk@awawa.club https://finit-project.github.io/#features is quite nice, long term project inspired by eeepc's proprietary init system has a lot of modern features such as cgroups, sd_notify, ...
But also, you seem to be a bit confused systemd is on the one hand an init system, but it's also a suite of a lot of smaller utilities that build upon the basic principles and features of the init system.
If your init rightfully already takes care running processes under certain user ids, cgroup, seccomp you might as well also define a container that way 🤷
Replying to
@zvyn@chaos.social
@zvyn@chaos.social you just have one major component less on your system, this allows a vanilla OS + the nspawn executables to provide containers. You're not dependend on another company but a well established project with long term maintenance track record.
Replying to
@mattiasb@mastodon.xyz
did u know, #systemd can now run #docker images natively, kinda
it's really nice
just needs two commands:
sudo importctl --class=machine pull-oci docker.io/library/alpine:latest alpine
sudo systemd-nspawn -M alpine /usr/bin/env sh -l
thank you @pid_eins@mastodon.social, I've spent several days/weeks in the past implementing this myself with hoops calling system-nspawn with my own docker layer overlayfs/bindmounts. Really hyped replacing this with that work.
drop caches just to be safe
safety first
patching third
Replying to
@arnar@floss.social
@arnar@floss.social Yes of course I didn't forget! How do you interact with the kubernetes API and how do you do state management? Sorry if I missed that. I feel that's the exciting part for me with what comes with nixops4, also because it integrates on a wider set of providers because of terraform providers.
:) your docs and website looks even better than last time I checked.
Is it just me or did @roberth@functional.cafe possible found the holy grail of nix kubernetes integration with #nixops4 native Terraform Provider integration?
Oh, great surprise seeing @troglobit@fosstodon.org #finit @ #NixCon presented by @aanderse@infosec.pub
Best part about good tools like NixOS are the daily appreciations you get to experience.
Really enjoying Kubernetes for the most part. Also the level of abstraction is just super cool, being able to operate on that level with resources and also the resource definitions themselves is just wonderfully powerful
kinda wish there was a combination of distributed deployments I get with Kubernetes but NixOS/system to describe each unit of service/system. kinda kubernixos
@sinza@bitbang.social hmmm interesting to know! I wonder what the lowest possible footprint is, `cryptsetup benchmark` might give some clues for low-memory methods. Key derivation function might also be something that has negative impacts on unlocking memory footprint
Seems stalwart is having some "enthusiasts" on GitHub that are mostly behaving rude and entitled. People fight over Dockerfiles over there 😆