This message was deleted.
# k3d
a
This message was deleted.
r
Does
docker image ls
do what you're looking for?
It's not exactly the same, but from using k3d with a standalone cluster I can say that adding images to the local docker daemon was sufficient for the k3d cluster to find them.
m
@rough-farmer-49135 Thank you for the comment. Are you saying you did not need to load the image using the
import
statement?
r
With K3D your cluster can get to any docker registry that your host can, and if you're air gapped then it can reference images that are known to your local docker daemon. So you can do
docker pull ${IMAGE_NAME}
or
docker load -i ${IMAGE_TARFILE}
and then reference the same containers in your cluster. However if you can pull from a container registry to get it you don't need to do those.
If you do bring them as tarfiles to an air gapped system and use
docker load -i ${IMAGE_TARFILE}
then you may need to do
docker image ls
to verify what the docker daemon loads it as (name, potential host, & version, which will match what it was on the host that created it so if you created it then you won't need to check).
m
@rough-farmer-49135 Perfect. Thank you for the explanation 🙂
👍 1