Ah, this is awesome! I currently run k3s on a decently spec-ed NixOS rig. I tried getting k3s to recognize my Nvidia GPU but was unsuccessful. I even used the small guide for getting GPU in k3s to work in nixpkgs[0], but without success.
For now I’m just using Docker’s Nvidia container runtime for containers that need GPU acceleration.
Will likely spend more time digging into your findings — hoping it results in me finding a solution to my setup!
I am unsure if this bug is only for the NixOS environment because its library paths and other quicks differ from those of major Linux distros.
Another major problem was that the "default_runtime_name" in the Containerd config didn't work as expected. I had to create a RuntimeClass and assign it to the pod to make it pick up the Nvidia runtime.
Other than that, I haven't tried K3S, the one I am running is a full-blown K8S cluster. I guess they should be similar.
While there's no guarantee, if you find any hints showing why your Nvidia plugin won't work here, I might be able to help, as I skip some minor issues I encountered in the articles. If it happens to be the ones I faced, I can share how I solved them.
By the way, one of the problems I encountered but didn't mention in the article was that the libnvidia-container has problem with the pathes for reading nvidia drivers and libraries under NixOS with its non-POSIX pathes. I had to create a patch for modifying the path files. I just created a Gist here with the patch content:
But later on, since I am taking the CDI route, it appears that the libnvidia-container (nvidia-container-cli) is not really used. If you are going with just container runtime approach instead of CDI, you may need a patch like this for the libnvidia-container package.
For myself, my blog and GitHub activity were key points in my interviews that heavily influenced my previous two hires.
> Also I can't decide what to write about, and whether to make it more nerdy or more professional.
Personally, I use my blog to write about:
- Niche things I run into that I want to document for myself
- Things I’m working on that I think are cool
- Opinions on why I do things a certain way
I love reading other blogs that orbit around this type of content. One suggestion I would make is to focus on writing your blog for yourself instead of a fictional audience. That way your blog’s value is self-contained, rather than worrying about the value other people get out of it.
I have no issue doing Arch installations by hand, but sometimes it’s nice to save time when you don’t have any special configurations. That being said, knowing how to do installations manually has been pivotal in me knowing how to recover borked Linux systems.
For anyone curious of why public latrines exploded:
> Even worse, these public latrines were notorious for terrifying customers when flames exploded from their seat openings. These were caused by gas explosions of hydrogen sulphide (H2S) and methane (CH4) that were rank as well as frightening.
> I’m looking forward to the new iPad Pros, but I can’t shake the feeling that the same old iPadOS cycle is about to begin all over again.
This is EXACTLY how I feel. WWDC will roll around and Apple will completely drop the ball for yet another year with iPadOS.
I also feel that the iPad Pro is one of the best hardware form factors for a computer — but iPadOS makes it a not great laptop replacement. I can’t help but feel like it would look incredibly foolish for Apple to do their May iPad event announcing M4 iPads — only to find out at WWDC that iPadOS still sucks.
Thankfully, it seems like most people, tech reviewers, etc. are vocal about iPadOS missing the mark. I hope Apple doesn’t continue to ignore the negative feedback.
Having an iPad Pro with an M1, I grow increasingly frustrated each year with how incapable my iPad is compared to my Macbook/Linux laptops. iPadOS still feels like iOS with some visual tweaks to the larger screen real estate. It’s absolutely not a laptop killer for a sysadmin or developer (unless your preferred language is Swift). Maybe it’s a laptop killer for creative professionals?
I think my iPad is an excellent thin client, however — but a Pro device should be more than just a thin client for me, imo.
Some things that would be a huge improvement for me:
1. Ability to do development locally
2. Virtualization (might circumvent the need to do local dev)
3. Install/build local applications
Apple seems determined to never allow anything outside of the App Store on i[Pad]OS, and with iPadOS being over four years old and still feeling like a giant iPhone, I don’t think I could recommend anyone should buy an iPad as a power user device.
Same. Don't buy an iPad! For real. It's a ridiculous device. Effectively no more useful than any other cheap tablet. Those tempting hardware features, you won't be able to use them in the end anyway, because of software limitations. You just can't do serious work with the iPad in practice. Trust me, after a short honeymoon period, and another few weeks of frustration, it will end up collecting dust and you will only ever rarely use it to watch movies at most.
If you buy one still, don't forget to turn it off completely, or you will find it someday, the battery completely drained and you realize it must have been months. Not good for battery health.
Yes, of course if you have a concrete, specific significant use case for the pencil it may be more appealing. But the pre M1 iPad with the pencil did the job as well, for drawing and pure handwriting. Obviously the iPad is marketed to be more than a single purpose device. The processing power is completely wasted. Most people probably won't use the pencil much in the long term.
It's file management, app limitations and interoperability which kill usefulness.
I love the iPad for its stylus, it’s a great device for brainstorming even with just notes. I wish there was more creative software they took advantage of the form factor however, like a touch/stylus based programming environment.
It is marketed to be more than a drawing device tho. It fails at anything but being a glorified scratchpad. Very narrow usefulness.
I got the first iPad (2016?) with pencil, for 400€, I think. It still does completely fulfill my needs for brainstorming. For anything else, the app ecosystem and locked down system are useless.
I agree that a lot could be improved on the iPad and I would not say no to the features you suggest. But I’m not sure I understand why you would want to use an iPad instead of a laptop as a developer. For me the whole thing with the iPad is the pencil. I would never use it for development tasks (maybe like some sort of emergency device while traveling).
Not saying you are wrong to want to use it for development, just curious why!
It would be the last device I ever need, if it did work like that... It actually hurts me, how its limitations are completely arbitrary and artificial. The iPad could be the best thing ever, yesterday. So, so frustrating and disappointing.
> simply because a terminal-driven workflow via SSH is at least possible
This has been the one thing that has kept my iPad useful! I use Blink (grandfathered into their Legacy Pro plan) and it’s a very clean experience. I can’t help but feel like it’s a fragile experience having to rely on an app from the app store for my iPad to be useful — that Apple or the Developer could remove at any time. Maybe it would feel less fragile if Apple provided an official i[Pad]OS Terminal/SSH client.
I recently started my own Mastodon instance for myself in this same train of thought. I noticed that one of my toxic traits was reaching out to people too often about things I found interesting. Expressing my own interests on my own Mastodon instance — even if nobody is looking at it — has been amazing for me to be more self-sufficient emotionally when it comes to my interests. It’s almost like a tech diary for me at this point.
Similar to parent, I find tremendous value in making myself my target audience.
I feel the same way. I wish they offered a second factor for SSH auth — when I last looked, they didn’t.
I also send myself notifications any time a failed or successful SSH login attempt occurs by tailing the ssh service with journalctl. When I last tried Tailscale SSH, it didn’t log anything to journalctl and so my self-notification via journalctl method did not work.
If you aren’t familiar, Nix-Darwin allows you to codify your MacOS deployments in a fashion comparable to NixOS. As a huge Nix-Darwin user myself, I have found malob’s repo extremely helpful for ideas with MacOS configuration. Nix-Darwin has made me so happy as a MacOS user. :)
Some other unsolicited tips:
1. Start with Nix flakes for configuration
2. Invest in Home-Manager before NixOS or Nix-Darwin
3. Ask people for help in Matrix or Discourse — my experience is that Nix-related folk are very welcoming and understanding
For now I’m just using Docker’s Nvidia container runtime for containers that need GPU acceleration.
Will likely spend more time digging into your findings — hoping it results in me finding a solution to my setup!
[0] https://github.com/NixOS/nixpkgs/blob/master/pkgs/applicatio...