I got you:

I got you:

+1 I finally finished my bachelor’s at 31 so I could check a box on job applications. I wouldn’t have my current position without it, useless and inapplicable though it is.


Love it. Gives a new meaning to JBOD too: junk box of disks!
I was going to buy the Lego Star Trek enterprise, but it was sold out before I got there. Oh well, they saved me from myself with artificial supply restrictions.
Instead, I didn’t buy anything.


There were decorations for sale at Costco in California in late August. Decorative gourd season decorations hadn’t even shown up yet.
I see. Yeah, that compose file is gross unless you’re running this on a dedicated vps, and even then…
I haven’t run snikket before, but it looks straightforward to me. Maybe the documentation has improved?
Once podman is installed (iirc the network package is marked as a dependency for most package managers) and your user is configured (provide subuids/subguids), I really think podman is a simpler model. The containers you run are actually yours (not root’s) and you don’t need to be part of a privileged docker group to run them. Of course, you can run containers as root with podman too: just use sudo.
You’ll actually need to configure your user the same way for running docker in rootless mode, which should be the default.
Your dockerfile will work with podman. Your docker-compose file will too (via podman compose). You’ll have access to awesome new capabilities like pods, and defining your containers with kubernetes style yaml, and running your containers via systemd.
However, with rootless podman/docker, you should remove any/all of the USER silliness the rootful/default docker people do to protect themselves a bit from rogue processes effectively running as root and/or container escapes to root.
Tiling WM and Gruvbox. Doesn’t get any better!


Yeah, it is pretty great!
I’m building software to bridge an in house legacy system and a CLI program. It has 1 partial restful API endpoint (no delete, no patch/put). But it does have 3 cyber security suites including one that wraps the runtime. It is not a public API.
I have 4 meetings a week.
Did I mention I work from home?


Going on 22 days waiting for a firewall rule change so I can pull containers from the enterprise GitHub enlistment.
I’ve had discussions with 4 different OUs. Not one of them has been able to tell me why the firewall is different for this VM. There is no way for me to see the state of each and compare.
I’ll probably come off as a crusader, but rootless Podman is a great way to accomplish this out of the box.
Podman maps your user ID to root in the container, but you don’t need root (or a rootful socket) to run the container.
Docker also has a rootless mode now, but I’ve found no reason to go back.


It seems like the only time I encounter this oddness is when some upstream docker image maintainer has done a weird with users (I once went 3 image levels up to figure out what happened).
Or if I borrow a dockerfile and don’t strip out the “nonroot” user hacks that got popularized years ago.


Next, he’ll be going around trying to get kicked out:
“Bun cha fools around here, I dare you to banh mi”.
Yes, the bubble is a pure speculation (growth) game. As long as the new shiny makes more people want in on the stock (public or private) continually, share prices grow and the company has continued runway.
Eventually, private equity exits with an IPO and the public gets a chance to be left holding the bag too.
AI product pushing, absolutely. I actually fairly shocked there isn’t more. Probably because they can’t actually predict the output.
“You can do get the most efficient results at the lowest TCO with [insert vendor’s product]!”
But you get ai answers with Google now so… It’s basically the same.
An hour of ideal developer time. Too bad there’s only 3 of 4 of those per quarter.


It’s perfectly representative of the opinion asked for.
Getting down voted is hilarious, because we’re admitting “fuck you, this is actually awesome.”
Well, that explains why corporate is so intent on them. They’re creating the perfect little KPI-driven stooge.
Heck, now I’d like to see a study on KPIs (as a concept) as a reality distortion lens. It would seem like they have inadvertantly created a way to calculate a reality alignment index for a given KPI. Is it reasonable to conclude that using KPIs to measure performance is, in itself, unethical behavior?
To go a bit further: Is there a correlation between the number of KPIs and the likelihood of creating scenarios in which the only desirable outcome lies outside reality? That is, how many KPIs does it take to get sufficient competition between priorities that it effectively requires hallucinating a solution to achieve a sufficiently aligned result?