It’s too late, we can’t contain it
Yeah, that ship has sailed.
Lol
Missing a comma: “Stop, use Docker.” But actually, use Podman.
Relatedly, a 2019 tweet from Solomon Hykes, the creator of Docker: https://x.com/solomonstre/status/1111004913222324225
If WASM+WASI existed in 2008, we wouldn’t have needed to created Docker. That’s how important it is. Webassembly on the server is the future of computing. A standardized system interface was the missing link. Let’s hope WASI is up to the task!
I think WASM/WASI still has a ways to go before that’s realistic, but I’d keep an eye on them for the future.
deleted by creator
If you’re thinking in terms of JavaScript, then you must not be aware that WASM/WASI is a vastly more ambitious project than you know.
deleted by creator
I think the very long-term goal is for it to be the universal virtual machine, for all front-ends and all back-ends, and for all popular programming languages. And given that its status on the browser has already been secured, I don’t think it’s impossible for the long-term vision to be reached, eventually.
As someone who has used and loved Docker since 2015, but never used Podman, can you explain the difference and why I might want to make the switch?
From a practical standpoint I’m really not qualified recommend one over the other, but the licensing is different. Podman also seems to be more “open source-y,” but I’m going on vibes here; perhaps someone more knowledgeable can elucidate.
Why would you recommend people make the effort to switch to Podman if you can’t name any benefits of doing so?
I would suggest that if someone is using neither, perhaps consider podman as open source. However, I too would need a reason to move. I mainly use synology for images, so its their container manager, rather than docker but my understanding is its docker under the hood.
edit: sorry, I replied to the wrong comment.
If you want to lose most of your tooling and community support, Podman is a great way to go.
From what I heard, podman doesn’t require root but that’s about it. On the other side, it’s a redhat thing and it’s not as popular which means less documented and less containers
Supposed to be an easy, if not a drop in replacement afaik, it’s under a permissive licence (Apache 2.0), beyond that it’s authored by RedHat I can’t tell you much else, it’s something I’ve been considering moving to personally (and work, pretty much for licencing and the few of us that want to use more open tech stacks) I just haven’t had a chance to work with it.
Supposedly able to pull docker images and work with docker-compose, just not swarm.
I honestly and truly don’t want to spend time relearning another system like this, especially one without decades of documentation and support available.
Depending on how old you are, eventually that choice may no longer be up to you.
My plan is to burn out soon, and work on projects for fun/side jobs. Corporate world has absolutely vacuumed my life long passion in the past 5 years.
Laughs in Proxmox + NixOS
(yes I know not for every usecase)
I dropped the proxmox part.
Nixos ftw
I’m waiting for the Proxmox NixOS project to take off. I like the (network) seperability.
images were meant to be trapped in cabinet files
