this post was submitted on 01 Jul 2025
93 points (91.2% liked)
Technology
72506 readers
3550 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
IMO: My personal problem with Docker is that it creates its own kind of vendor lock-in. Docker does not run on the server operating systems I use. The tendency is towards a Linux monoculture and that is never a good idea. Docker is a symptom, not a solution.
Is it really vendor lock-in if you can fork it at your whim?
forking doesn't really help with the underlying problem that docker is a layer to run on top of Linux's KVM. at a certain point though, it's become standard enough though that BSD not having a good way to support docker, or any other CRI containerization service for that matter, is a BSD failure, not a containerization failure
My understanding is that this is only true for docker desktop, which there's not really any reason to use on a server.
Sure, since containers use the host's kernel, any Linux containers do need to either have Linux as the host or run a VM (as docker desktop does by default), but that's not particularly unique to docker
podman exists and doesn't force root...
That's true, but all of their problem with docker are that it's Linux
Sounds like a them problem then.