X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=w4V4ffLuxJuZNx3I
	LTTDR3Zr8f7q7wDHQmJBmxfmRQUEWy34YBKarp9Lf8CSlL7uMgeVgF0FsWx/bkkm
	leLxqAe/LAqN9y+ds3kt8OFFUXKbsvqR1uzlHTFjrmL6T+XSrK/bqnjndiq6gszE
	fjAWO1Lu6gJXkTCM9QZs3aCo+W4=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=ft8ufTG0NIPSrI5yJAA47T
	TYS00=; b=XOcPpYqVRCylcZjXrHeySbN+vuIxuqTls9GQ9aOZW6ZN27gfQKj4BP
	j4WLBN+Necgu6pajqwFoFlau4PuvCPI/moKAblXP73xpScobY1LJtPHnIGLw6GaB
	y6ioqU+dmfaXhvjv0zAFOUiHCyMRs8DXiLBdS5fv5oKsqfIm3NG1Y=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Spam-SWARE-Status:	No, score=-0.9 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2 spammy=31072018, 31.07.2018
X-HELO:	mout.kundenserver.de
Subject:	Re: Any reason Cygwin might prevent kubectl exec from showing shell prompt?
To:	cygwin AT cygwin DOT com
References:	<CAA5t8VqgNm+-wGn+iF-LtXUoFKL9+m=zH4=A959B0YsMGEqVmw AT mail DOT gmail DOT com>
From:	Thomas Wolff <towo AT towo DOT net>
Message-ID:	<6646b33b-ed7f-1078-6754-12259bf094e7@towo.net>
Date:	Tue, 31 Jul 2018 18:27:52 +0200
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version:	1.0
In-Reply-To:	<CAA5t8VqgNm+-wGn+iF-LtXUoFKL9+m=zH4=A959B0YsMGEqVmw@mail.gmail.com>
X-IsSubscribed:	yes

Am 31.07.2018 um 18:15 schrieb David Karr:
> 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.
This may be an instance of the pty incompatibility issue of native 
Windows programs (which I assume kubectl to be).
Try `winpty kubectl`, after installing winpty, that is.
Maybe someone should put up a winpty cygwin package; maybe I should do it...

> 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.
You may have set PS1 in your .profile (or .bashrc) but not exported it 
into the environment (export PS1).

--
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

- Raw text -