Getting Started

[claywd]

Just started looking at this today. Want to get this working on wsl so I can get k3d creating clusters without rancher or docker desktop. couple of questions.

1. I assume installation just consist of make install from the project. Correct me if I'm wrong.
2. Nerdctl is already symlinked as the docker bin so all the docker commands pass but curl --unix-socket /var/run/docker.sock http://localhost:2375/_ping does not... do we need to symlink var/run/docker.sock and nerdctld.sock?
3. If you want to join kubefirst-community on slack we can hack some of this out and try to get it working on WSL as well. Happy to contribute examples and what not.

[afbjorklund]

There should be no need to mess with the original docker.sock, but you do need a "real" docker client to communicate

The curl thing was just an example of "What Would Docker Do", you can do the same with the nerdctl.sock as well

i.e. sometimes it is hard to guess what the request/response looks like, just from reading the API specification

So then I use curl to see what the low-level looks like, there is also a log where "gin" dumps the web requests

[afbjorklund]

This repository could probably do with some "reasonable expections", on what it is supposed to be doing...

Note that competing with Docker is not the goal of nerdctl.

The main features are load and build, for use with containerd clusters in minikube. The others are list/inspect.

https://github.com/afbjorklund/nerdctld#implemented-commands

[claywd]

Okay. One thing I was hoping to do was get containerd, nerdctl, nerdctld, and k3d playing nicely inside wsl2 but without the full set of api commands I doubt that will be possible. There is also variaous drivers missing on wsl2 that nerdctl and k3d native expect. I'm guessing this is currently way outside the scope of what you're trying to accomplish.

[afbjorklund]

The end goal would be to have the nerdctld API support the same commands as the nerdctl CLI:

https://github.com/containerd/nerdctl/blob/main/docs/command-reference.md

Some features might require small tweaks to nerdctl, on the server side, before they would work OK...

But it would be nice to have basic "run" support, so that docker buildx and vscode-remote can start?