This message was deleted.

the rancher/rancher image isn’t supported for anything except for dev/eval use. Rancher is also not meant to be used to manage standalone containers, it is just a Kubernetes management tool.

Thank you. I meant to deploy a container in K8S via Rancher just like we do on the commandline with docker run. I'll look for info on K8S w/r to existing docker artifacts.

that would be a pod then. Yes, you can create pods.

I know. It's just that apparently existing docker artifacts on the host do not show up. Maybe that is due to Rancher running in docker itself.

if you’re using the rancher/rancher image, it is actually running a full K3s cluster using containerd, inside Docker. That cluster doesn’t use docker and isn’t aware of it whatsoever. Honestly I think what you are trying to do probably matches Rancher Desktop better than Rancher.

I use Rancher Desktop on my personal laptop and indeed I can see my local Docker artifacts. I was just trying to deploy a K8S service using a docker image on the host where the Rancher docker container we're testing is running. On the one hand we run the image direclty with Rancher; on the other we launch that same image in Rancher e.g. on another port. I'll dig deeper. Thank you.

Rancher Desktop jumps through a bunch of hoops to make that easy for you. Once you move into deploying stuff to a full Kubernetes cluster (in particular one that doesn’t use Docker as the container runtime) you really should start making use of a private registry.

Right. Thank you.