#nerdctl — Public Fediverse posts

Managing containers using #nerdctl compose in an IPv6-only environment is aggravating, not least due to non-intuitive default behavior like all v6 nameservers being stripped from /etc/resolv.conf .

But I choose not to blame the Nerdctl developers, as their implementation intentionally tracks that of Docker Engine. Docker themselves are responsible for royally messing up network understanding for a whole generation of developers, ruining the excellent use-case of #IPv6 for scaled-up containers.

Managing containers using #nerdctl compose in an IPv6-only environment is aggravating, not least due to non-intuitive default behavior like all v6 nameservers being stripped from /etc/resolv.conf .

But I choose not to blame the Nerdctl developers, as their implementation intentionally tracks that of Docker Engine. Docker themselves are responsible for royally messing up network understanding for a whole generation of developers, ruining the excellent use-case of #IPv6 for scaled-up containers.

Managing containers using #nerdctl compose in an IPv6-only environment is aggravating, not least due to non-intuitive default behavior like all v6 nameservers being stripped from /etc/resolv.conf .

But I choose not to blame the Nerdctl developers, as their implementation intentionally tracks that of Docker Engine. Docker themselves are responsible for royally messing up network understanding for a whole generation of developers, ruining the excellent use-case of #IPv6 for scaled-up containers.

Managing containers using #nerdctl compose in an IPv6-only environment is aggravating, not least due to non-intuitive default behavior like all v6 nameservers being stripped from /etc/resolv.conf .

But I choose not to blame the Nerdctl developers, as their implementation intentionally tracks that of Docker Engine. Docker themselves are responsible for royally messing up network understanding for a whole generation of developers, ruining the excellent use-case of #IPv6 for scaled-up containers.

Managing containers using #nerdctl compose in an IPv6-only environment is aggravating, not least due to non-intuitive default behavior like all v6 nameservers being stripped from /etc/resolv.conf .

But I choose not to blame the Nerdctl developers, as their implementation intentionally tracks that of Docker Engine. Docker themselves are responsible for royally messing up network understanding for a whole generation of developers, ruining the excellent use-case of #IPv6 for scaled-up containers.

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 🤓

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 🤓

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 🤓

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 🤓

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 🤓

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?

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?

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?

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

#codeberg #translation

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

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

#codeberg #translation

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

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

#codeberg #translation

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

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

#codeberg #translation

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/

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/

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/

#nerdctl #containerd

https://github.com/containerd/nerdctl