kind cluster - how to see docker-images that are loaded?

k1eran

20 Sept 2024, 23:37 UTC

122.1K views1

To test my images I normally load them into my kind cluster by running on my macOS laptop something like ...

kind load docker-image foo/bar-1.0.0:latest

How do I see what images have already been loaded ?

kind = https://github.com/kubernetes-sigs/kind

docker

kubernetes

1,208 following

1 answer

Accepted answer · original discussion

Arghya Sadhu

22 Sept 2024, 11:37 UTC

Permalink

Get name of a node by running kubectl get nodes.

Get into the node by running docker exec -ti <nodename> bash

After getting into the node you can just run crictl images to see images loaded on that node.

Your perspective belongs here.

Join the conversation

2 question comments

Use comments to ask for clarification. Post a solution as an answer.

PjoterSPermalink

23 Sept 2024, 23:37 UTC

Do you mean to list all images like docker images? docs.docker.com/engine/reference/commandline/images

k1eranPermalink

25 Sept 2024, 11:37 UTC

@PjoterS yes but for INSIDE the kind cluster itself. Answer from Arghya has given me enough to move on.

Keep exploring this topic

What considerations should guide the containerization and Kubernetes deployment of a Ballerina service to maintain portability, observability, and resource efficiency?

Deploying a Ballerina service as a Docker container and running it in a Kubernetes cluster involves compiling the source to a native binary, building an image that contains the runtime, and defining manifests that describe pods, services, and scaling policies.

Mongo DB deployment not working in kubernetes because processor doesn't have AVX support

I am trying to deploy a mongo db deployment together with service, as follows: apiVersion: apps/v1 kind: Deployment metadata: name: mongo-deployment labels: app: mongo spec: replicas: 1 selector: matchLabels: app: mongo template: metadata: labels: app: mongo spec: containers: - nam

Docker standard_init_linux.go:228: exec user process caused: no such file or directory

Whenever I am trying to run the docker images, it is exiting in immediately. CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES ae327a2bdba3 k8s-for-beginners:v0.0.1 "/k8s-for-beginners" 11 seconds ago Exited (1) 10 seconds ago focused_booth As

Error pulling docker image from GCR into GKE "Failed to pull image .... 403 Forbidden"

Background: I have a GKE cluster which has suddenly stopped being able to pull my docker images from GCR; both are in the same GCP project. It has been working well for several months, no issues pulling images, and has now started throwing errors without having made any changes. (NB: I'm generally the only one on my team who accesses Goog