https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# k3d
a
This message was deleted.
w
I think the 
image import
functionality has a bug of failing silently which has to be fixed. It's not on every run?
m
No, it's not on every run, but quite often
w
Are you importing multiple images in a single command? Are you importing from tarball or from image store?
m
I'm importing 6 images with a single call to 
k3d image import ..
. I'm importing docker images that's on the local system. They've just been built with docker build
w
Alright, thanks for the input 👍
m
Anything I can do to catch the silent error somehow?
Or to help debug it further?
I found a few existing issues on the repo for this. I'll study those first. Sorry for not checking
Is there anything more than adding 
--trace
to the image import command I can do to get more information about what's happening? I have an example of the trace logs now, where the image import seems to go ok, but the pods fail with ImagePullBackoff errors, but I don't think the logs are revealing anything.
f
Yes, it happened to me also when importing specifically an image with the tag 'latest', I changed the tag to 'test' and it worked, probably anything but 'latest' will work
m
I walked into that issue previously, causing me to change all tags to "local" instead of "latest". So it's not that issue right now 🙂
f
I would try and view the logs on the k3d docker worker containers, the ones that act like the hosts
Would also try to view current events using kubectl: 
kubectl get events --sort-by='.lastTimestamp'
m
Thanks! I'll add those two also, so that I may have more info the next time this happens
4 Views
Open in Slack
PreviousNext
Powered by