kubectl logs ... --previous ? On Wed, Jan 31, 2018 at 6:38 AM, Colstuwjx <colstu...@gmail.com> wrote: >> >> >>> >>> But, what if we want to trigger the detail exited reason for the exited >>> containers? Is there any parameters configure that? >> >> >> Have you checked the terminationGracePeriod? I think it will do just that. > > > I'm afraid not, I need to check the exited container, such as some container > with wrong configurations, and determine the root cause. > After the `terminationGracePeriod `, the unhealthy container would be > deleted, and we can't do things like `docker inspect <exited_pod_container>` > to trigger that case. > > -- > You received this message because you are subscribed to the Google Groups > "Kubernetes user discussion and Q&A" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to kubernetes-users+unsubscr...@googlegroups.com. > To post to this group, send email to kubernetes-users@googlegroups.com. > Visit this group at https://groups.google.com/group/kubernetes-users. > For more options, visit https://groups.google.com/d/optout.
-- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
