In 10 minutes, I changed from #docker to #nerdctl it was a smooth change, I did it because I liked the name of nerdctl

https://github.com/ozkanpakdil-redgate/docker-sandbox/blob/nerdctl-containerd/postgres17-ubuntu/setup.ps1

I do not see any big difference between, I wonder about performance, it felt like same too, but love to hear some numbers on this

Please let me know if this is helpful to chart the post-Docker Desktop virtualisation/containerisation space.

After over a year I gave up using #docker alternatives, e.g. #containerd + #nerdctl. Too much stuff is not working out of the box. Pretty sad that there is still no real alternative.

I feel I'm on the cusp of an adventure I really don't want to start. In short: #nerdctl + Compose + #IPv6

I suspect it will be awful, seeing as nerdctl duplicates the #docker commands, which only recently supported IPv6. And then there's the whole business of IPAM for containers, whether they use NAT66 and ULAs -- ugh -- or rely on SLAAC and native networking.

I wanted Compose for #k8s like orchestration but simplified for single machine operations. Why must this IPv6 journey be so hard?

#Nerdctl の #和訳 #プロジェクト のリポジトリはこちらです。 #OmegaT と #mkdocs を使ったプロジェクトになります。

https://codeberg.org/miurahr/nerdctl-docs-ja

There was #rancher and #podman, now #AWS shares #finch, a new open-source solution build on top of #lima #nerdctl #containerd and #buildkit for building, running and publishing Linux containers on MacOS. https://aws.amazon.com/fr/blogs/opensource/introducing-finch-an-open-source-client-for-container-development/

Ok. I'm blaming @vcsjones for the rabbit hole I'm currently stuck in.

Has anybody running #nerdctl on #linux ever run into an issue like this when trying to run containers?

@vcsjones I saw your post about #nerdctl yesterday. How did you install (and how did you get the dependencies properly installed)?

Setting up a new dev machine and want to give it a shot over Docker.