https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# k3d
a
This message was deleted.
r
Docker runs the servers & agents you run in K3D as containers, along with a load balancer (for each, I think, though I usually do one node so it's been a while for me to be certain). The K3S instance that's running in the server & agent container is using containerd to run your containers and those won't show up in Docker as they go through a different interface/socket. I don't recall how to do it from the host, but you'd need to query with ctr, nerdctl, or crictl to see containers running in Kubernetes.
e
I see the main components through `docker ps`:
Copy code
NAMES
k3d-dev3d-tools
k3d-dev3d-serverlb
k3d-dev3d-server-0
k3d-dev-registry
just not the containers in my pod
r
Yep, that's what I'd expect. Though I don't do my registry through k3d so I see a separate one and the tools container is only transient for me as well.
If you do a docker exec into the k3d-dev3d-server-0 container you should be able to try the ctr or crictl commands from https://gist.github.com/superseb/3b78f47989e0dbc1295486c186e944bf (just substitute k3s for rke2) and I think you'll see them from there. Though I might be misremembering and you'll only see the static pods and not the running pods.
Either way, the containers don't run through the docker daemon and run through a different container runtime is why you can't see them with 
docker ps
is the short answer.
e
yeah, that worked. exec + 
ctr c list
thanks!
👍 1
r
Yep. Different container runtime, which is where it doesn't show your containers you see from 
docker ps
.
I kinda' wish I knew a way to request to see all containers in all runtimes, but I don't think that exists.
But that's also the thing about open source, we take what we can get if we aren't motivated and/or talented enough to create the things we're hoping for ourselves and contributing them.
e
true
56 Views
Open in Slack
PreviousNext
Powered by