DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:from:date:message-id:subject:to
	:content-type; q=dns; s=default; b=ZUeEKoXOF9nkiLWD/h7JFIrUWV+9q
	VlNEgaeEqr5qUX2gNHfCiQOB8T6nqpcGPybVKK7iv+dRlXo9aukokG5/ce5uZvu0
	WRIxKJik1QeAWwQ3cKFy+qgkZ03bK/x6lpRYrY8T0U1yJu6YI5oMs9/3mfLNuH89
	2kYY1A6GAiwddQ=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
MIME-Version: 1.0
From: David Karr <davidmichaelkarr AT gmail DOT com>
Date: Tue, 31 Jul 2018 09:15:21 -0700
Message-ID: <CAA5t8VqgNm+-wGn+iF-LtXUoFKL9+m=zH4=A959B0YsMGEqVmw@mail.gmail.com>
Subject: Any reason Cygwin might prevent kubectl exec from showing shell prompt?
To: The Cygwin Mailing List <cygwin AT cygwin DOT com>
Content-Type: text/plain; charset="UTF-8"

I really have no idea if this is a Cygwin problem, just trying to eliminate
variables.

I believe my Cygwin version is "2.9.0(0.318/5/3)" (from the uname string).

From a mintty window, I use a variation of "kubectl exec" in a script to
run a shell in a container in a pod.  It appears to run, and I can run
processes from that shell in the container, but the curious thing is that I
never get a shell prompt from the container.  I thought I had gotten this
to work before, in the same k8s cluster, but I'm not certain.

The other curious thing I see is that if I execute "echo $PS1" in the shell
in the container, it gives me a reasonable response ("\w \$"), but if I
instead do "env | grep PS1", it returns nothing.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple