databricks / click

The "Command Line Interactive Controller for Kubernetes"
Apache License 2.0
1.49k stars 84 forks source link

logs not working #43

Closed omerlin closed 6 years ago

omerlin commented 6 years ago

hello,

I'm inside a pod and i want to see the logs [admin-context] [smdp4] [consumer-profile-stock-1387439186-s6pvb] > logs error: The following required arguments were not provided:

USAGE: logs [FLAGS] [OPTIONS] For more information try --help So i tried to give the container name even if i thing we should not need (we are "in" the pod): [admin-context] [smdp4] [consumer-profile-stock-1387439186-s6pvb] > logs consumer-profile-stock Hyper error: failed to lookup address information: Name or service not known Any idea ? cheers
nicklan commented 6 years ago

Hrmm that's odd. So for pods with one container the next release (or master) will default to that container for logs (see #25).

The second error is odd. could you paste the output of the containers command when you have selected that pod. Also, how many nodes are in your cluster?

nicklan commented 6 years ago

I'm pretty sure I fixed this in #46. If you're building click yourself, would you mind updating to latest master and testing?

Thanks!

omerlin commented 6 years ago

Hello Nick, Rebuilding from source works well and solve the logs issue. Thanks a lot cheers

nicklan commented 6 years ago

great, glad to hear it. thanks for closing :)