This message was deleted.

you mean nerdctl.toml? config.toml would be for containerd running in the rancher-desktop distro

I suppose I am looking for the nerdctl.toml? My google-foo pointed me towards looking for a nerdctl/config.toml file, but I'm also not finding the nerdctl.toml file. I was wrong about WSL, by the way - looks like it was set up also, but I couldn't connect to \\wsl$<directory> like I was seeing in certain search results.

so i don't think they use nerdctl.toml, but nerdctl can read .docker/config.json as well depdning on the config. i believe the nerdctl is just a stub in the Host so you will want to use

rdctl shell

to jump into the VM and then create a ~/.config/nerdctl/nerdctl.toml i believe

OK. Thank you for the info. I wasn't aware of the

rdctl

command - that's much appreciated. Let me get to the core question I was trying to answer by looking at the config files. I was surprised yesterday when I did a build that the package appeared to be published to docker.io, but was in fact published to the rancher desktop. My assumption was that nerdctl had a config line somewhere saying "my registry is named X and is located at Y". Do you know how that's configured?

you mean it was built local. did you try and push it to a registry?

I did not try to push it elsewhere, local only. So the behavior was correct but the text returned was misleading.

thats the default tag for any image.

You would not be able to push to

<http://docker.io/library/*|docker.io/library/*>

anyways because that is a reserved namespace for default images from Docker. Locally you can name your images however you want

Please forgive the neophyte questions 🙂 Thank you for your patience. I appreciate the information.