This message was deleted.
# rancher-desktop
a
This message was deleted.
k
I don't completely follow -- if the image is listed in the UI, then there's no need to pull it. But if you want to pull another image, the command is
nerdctl -n <http://k8s.io|k8s.io> pull IMAGE
.
You can actually specify other namespaces with the
-n
option (or provide no namespace at all, which will put it in the
default
namespace.
m
Correct. However, when building an image using a FROM <IMAGE> in a Dockerfile that uses that image it attempts to find the image at docker.io, not in the set of images that is locally available.
Do I need to tell my
nerdctl build ...
command about the local image in some way?
k
I think all local images have to be pushed to an external repository, but let me check....
b
https://itnext.io/containerize-a-basic-html-css-js-app-with-nerdctl-rancher-desktop-817981ede2a4 Yeah I had to use the -n option to build, see that article as an example.
nerdctl -n <http://k8s.io|k8s.io> build . -t jwsy/shooter-jade:v1.0
m
That FROM is for something in an external registry, not something built locally.