HNHacker News
TopNewBestAskShowJobs

bmitch3020

746 karma · joined September 5, 2017

OSS maintainer of OCI projects, including regclient, olareg, and a few of the specs.
submissionscomments
bmitch3020··on How I estimate work
Except if you've already done a very similar project before, the unknowns are now knowns. And more importantly, problems already have developed solutions that can be copied or reused, and not developed. So a very similar project should be an overestimate, and a repeated task should take a fraction of the first time.
bmitch3020··on What has Docker become?
Another year, another story written about the demise of Docker. This has been happening since before Kubernetes took off. My own take:

Docker had a choice of markets to go after, the enterprise market was being dominated by the hyperscalers pushing their own Kubernetes offerings. So they pivoted to focus on the developer tooling market. This is a hard market to make work, particularly since developers are very famous for not paying for tooling, but they appear to making a profit.

With Docker Hub, it's always been a challenge to limit how much that costs to run. And with more stuff being thrown in larger images, I don't want to see that monthly bill. The limits they added hurt, but also made a lot of people realize they should have been running their own mirror on-prem, if not only to better handle an upstream outage when us-east-1 has a bad day.

Everything else has been pushing into each of the various popular development markets, from AI, to offloading builds to the cloud, to Hardened Images. They release things for free when they need to keep up with the competition, and charge when enterprises will pay for it.

They've shifted their focus a lot over the years. My fear would be if they stayed stagnant, trying to extract rents without pushing into new offerings. So I'm not worried they'll fail this year, just like I wasn't worried any of the previous years when similar posts were made.

bmitch3020··on What has Docker become?
You're missing image distribution, namespaces (networking, pids, mount, users), seccomp (to limit root powers), cgroups (to limit cpu and memory usage), and so much more. There's also Docker Hub with the official images they maintain. And the Desktop tooling makes an embedded Linux VM much easier to work with than spinning up your own VM, copying files around, and forwarding networking ports.
bmitch3020··on What has Docker become?
Gordon unfortunately passed away in 2023: https://x.com/solomonstre/status/1637537983988629504
bmitch3020··on What has Docker become?
> What I hate about docker and other such solutions is that I cannot install it as nonroot user

There's a rootless [0] option, but that does require some sysadmin setup on the host to make it possible. That's a Linux kernel limitation on all container tooling, not a limitation of Docker.

> and that it keeps images between users in a database.

Not a traditional database, but content addressable filesystem layers, commonly mounted as an overlay filesystem. Each of those layers are read-only and reusable between multiple images, allowing faster updates (when only a few layers change), and conserving disk space (when multiple images share a common base image).

> I want to move things around using mv and cp, and not have another management layer that I need to be aware of and that can end up in an inconsistent state.

You can mount volumes from the host into a container, though this is often an anti-pattern. What you don't want to do is modify the image layers directly, since they are shared between images. That introduces a lot of security issues.

[0]: https://docs.docker.com/engine/security/rootless/

bmitch3020··on What has Docker become?
I agree with a lot of the above, but then there's:

> Docker is still maintaining the runtime on which orbstack, podman etc are all using, and all the cloud providers are using

I need to fact check that one. runc was donated by Docker to OCI a while back. And containerd was created under the CNCF from a lot of Docker code and ideas. podman is sitting on the RedHat containers stack, which has their own code base. Docker itself uses runc and containerd, and so do most Kubernetes deployments. Many of these tools go to containerd directly without deploying the Docker engine.

bmitch3020··on A free and open-source rootkit for Linux
Previously discussed at https://news.ycombinator.com/item?id=46498658
bmitch3020··on What twenty years of DevOps has failed to do
DevOps only failed in that so many don't know what it is.

DevOps isn't a tool, but there are lots of tools that make it easier to implement.

DevOps isn't how management can eliminate half the org and have one person do two roles, specialization is still valuable.

DevOps isn't an organization structure, though the wrong org structure can make it fail.

DevOps is collaboration. It's getting two distinct roles to better interoperate. The dev team that wants to push features fast. And the ops team that wants stability and uptime.

From the management side, if you aren't focused on building teams that work well together, eliminating conflicts, rewarding the team collectively for features and uptime, and giving them the resources to deliver, that's not a DevOps failure, that's a management failure.

bmitch3020··on Lock-Picking Robot
It's not picking, it's brute forcing every combination. Lishi and other lockpicks require tension and feedback, often one pin at a time, which is the opposite of what this tool is doing.
bmitch3020··on The spectrum of isolation: From bare metal to WebAssembly
The spectrum comes with multiple tradeoffs, and isn't a simple "bare metal is more secure" narrative. Because as you move into VMs, containers, and code sandboxes, you lose isolation which increases risks, but you also gain capabilities to limit the application which decreases risk. So I believe the most secure approach is layered with much multiple types of isolation working together.

For example, you may isolate a specific customer to bare metal so an escape doesn't compromise other customers. But within that bare metal, you may run containers because they make it easier to work with a read only root filesystem that's also trivial to upgrade. You can also add on user namespaces and seccomp in the container to minimize the risk of a container escape. And then the application may have its own sandbox that limits individual capabilities and which API calls it can run.

Every use case is different, and some layers may not be available depending on that use case. But rather than picking one point on the spectrum, one should pick a list of technologies that best solve each use case.

bmitch3020··on The URL shortener that makes your links look as suspicious as possible
I was able to get past that (Firefox on the Desktop) by clicking the "see details" button and then clicking the "ignore the risk" link. It took me a while to actually read the text too.
bmitch3020··on Drones that recharge directly on transmission lines
There's also powerline communication that these drones could use, relaying a signal to a second drone perched back in friendly territory. And if the military is going around blowing up all of their power transmission lines, that's also going to hurt them.
bmitch3020··on Drones that recharge directly on transmission lines
A jammed drone that's perched on a power line wouldn't fall out of the sky, and doesn't need to transmit 24x7, only when it detects some activity. The lack of a signal from it would itself be a signal of where the next attack is coming from. Anti-jamming weapons (missiles and autonomous drones) would also be useful, that lock on to any signal jamming sources and deliver the munitions directly to the target that's advertising itself.
bmitch3020··on Drones that recharge directly on transmission lines
I'm surprised this isn't already happening in Ukraine. They could fly small surveillance drones deep in enemy territory, perch on a power line, and send back lots of data. Not just video, but also sound and triangulating signals. This would also be useful in fog by monitoring major roads where high altitude drones and satellites would be obstructed.
bmitch3020··on Favorite Tech Museums
NSA's National Cryptologic Museum[0] is a good one in the DC area. There's also the Smithsonian Air & Space, but that gets outside of the tech focus here.

[0]: https://www.nsa.gov/museum/

bmitch3020··on Total monthly number of StackOverflow questions over time
As someone that spent a fair bit of time answering questions on StackOverflow, what stood out years ago was how much the same thing would be asked every day. Countless duplicates. That has all but ceased with LLMs taking all that volume. Honestly, I don't think that's a huge loss for the knowledge base.

The other thing I've noticed lately is a strong push to get non-programming questions off StackOverflow, and on to other sites like SuperUser, ServerFault, DevOps, etc.

Unfortunately, what's left is so small I don't think there's enough to sustain a community. Without questions to answer, contributors providing the answers disappear, leaving the few questions there often unanswered.

bmitch3020··on NY Fed cash transfers to banks increase dramatically in Q4 2025
Thanks. Here's an alternate Reuters link: http://archive.today/GWDYr
bmitch3020··on List, inspect and explore OCI container images, their layers and contents
This project even depends on go-containerregistry. Also in this space is RedHat's scopeo, Microsoft's oras, and my own regctl.

And my favorite project for inspecting layers is Jon's https://oci.dag.dev/.

bmitch3020··on Drugmakers raise US prices on 350 medicines despite pressure
http://archive.today/Gxx7p
bmitch3020··on Karpathy on Programming: “I've never felt this much behind”
https://xcancel.com/karpathy/status/2004607146781278521
bmitch3020··on Ask HN: Anti-AI Open Source License?
1. AI training companies don't care about your license, they'll still train on your software regardless.

2. Your software needs to be distributed with a license that is compatible with your dependencies. You can't add restrictions if your dependencies forbid that.

3. No one will use your project if it doesn't have an OSI license. It's not worth the time and effort to read every license and get it approved for use by the legal team. If you're doing anything useful, someone will make an alternative with an OSI license and the community will ignore your project.

bmitch3020··on Liberating Bluetooth on the ESP32
C3 also pushes to YouTube: https://youtu.be/q-_YVIIrF6A
bmitch3020··on Publishing your work increases your luck
Absolutely. I say that being an OSS maintainer is a job, which can easily become a full time job, where the pay is often non-existent. If you have a separate full time job, you now have to choose:

1. Work two jobs until you burn out.

2. Quit your paying job and hope you have you don't go broke.

3. Scale back or quit maintaining OSS projects.

I think companies, governments, and societies could do a better job funding this work. But since this is a "tragedy of the commons" problem, I'm not holding my breath that this will happen before the public experiences a lot more pain from failures.

bmitch3020··on Rob Pike goes nuclear over GenAI
Printed letters are less appreciated because it shows less human effort. But the words are still valued if it's clear they came from someone with genuine appreciation.

In this case, the words from the LLM have no genuine appreciation, it's mocking or impersonating that appreciation. Do the people that created the prompt have some genuine appreciation for Rob Pike's work? Not directly, if they did they would have written it themselves.

It's not unlike when the CEO of a multi-national thanks all the employees for their hard work at boosting the company's profits, with a letter you know was sent by secretaries that have no idea who you really are, while the news has stories of your CEO partying on his yacht from a massive bonus, and a number of your coworkers just got laid off.

bmitch3020··on Rob Pike goes nuclear over GenAI
The signal to noise ratio cannot be ignored. If I ask for a list of my friends phone numbers, and a significant other can provide half of them, and a computer can provide every one of them by listing every possible phone number, the computer's output is not something we should value for being more complete.
bmitch3020··on A faster path to container images in Bazel
Buildkit can be very efficient at caching, but you need to design your image build around it. Once any step encounters a cache miss, all remaining steps will too.

I'd also avoid loading the result back into the docker daemon unless you really need it there. Buildkit can output directly to a registry, or an OCI Layout, each of which will maintain the image digest and support multi-platform images (admittedly, those problems go away with the containerd storage changes happening, but it's still an additional export/import that can be skipped).

All that said, I think caching is often the wrong goal. Personally, I want reproducible builds, and those should bypass any cache to verify each step always has the same output. Also, when saving the cache, every build caches every step, even if they aren't used in future builds. As a result, for my own projects, the net result of adding a cache could be slower builds.

Instead of catching the image build steps, I think where we should be spending a lot more effort is in creating local proxies of upstream dependencies, removing the network overhead of pulling dependencies on every build. Compute intensive build steps would still be slow, but a significant number of image builds could be sped up with a proxy at the CI server level without tuning builds individually.

bmitch3020··on A faster path to container images in Bazel
> The current recommendation is rules_oci, which takes the opposite approach: use only off‑the‑shelf tools...

I'm the author of one of those off the shelf tools, and the rules_oci decision here always struck me as a bit unusual. OCI is a relatively easy spec with a number of libraries that implement it. Instead of creating a custom build command that leveraged those libraries to be an efficient build tool, they found commands that could be leveraged even if image building wasn't their design.

It looks like rules_img is taking that other path with their own build command based on the go-containerregistry library. I wish them all the best with their effort.

That said, if all you need to do is add a layer to an existing base, there are tools like crane [0] and regctl [1] that do that today.

The reason other build tools typically pull the base image first is to support "RUN" build steps that execute a command inside of a container and store the filesystem changes in a new layer. If that functionality is ever added to rules_img, I expect it to have the same performance as other build tools.

[0]: https://github.com/google/go-containerregistry/blob/main/cmd...

[1]: https://regclient.org/cli/regctl/image/mod/

bmitch3020··on Is Northern Virginia still the least reliable AWS region?
This story missed a glaring detail. There are simply more data centers in northern VA [0]. More than the rest of the US by a wide margin, or the entire EU+Asia. Things break here because it's where most things are.

[0]: https://www.datacenters.com/providers/amazon-aws/data-center...

bmitch3020··on LoongArch architecture added to Debian Ports
That's the "initial bootstrap" announced back in 2023. Today's announcement is being discussed at https://news.ycombinator.com/item?id=46334333
bmitch3020··on America's collapsing consumption is the disenshittification opportunity
This doesn't give a lot of hope for what's happening in America. But for those outside of the US, there's already a push to avoid US tech businesses. They prefer local clouds, ideally those run by non-US companies. And there's a lot of effort to shift to Linux on their government machines. While that hurts the US soft power, it improves their resilience from monopolies in the US, and I'm all for that.
← PreviousPage 3 of 4Next →