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:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:content-type; q=dns; s=default; b=FHgUY46
	C0o3G0hUdNE6mlxlm0B1O8Pnb4X6llBLcVETvu8SSrg4Xl4zsYk3A2CHGMQ5ubrt
	Q//e7AMPwkFNa7n4ASIRnG8emZmYrVgiNQwvIYpy9bG3xxO7jGJbijzrdoe687vb
	1BC5H+il2lHzm3RAJ6TtrTIVLNzfn6SflHRI=
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:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:content-type; s=default; bh=5+e13Kiv30GvR
	59yEI6G/iKKaxs=; b=V5gTrmCDsnkNsER1vFCznb2zP7vO4k3dhxrnuz5z7gKvs
	T76I6DIucs/gGrO9DTTybPE37HeK4WRh6jqb6LpXAHgBaDl11x1/63NwL+DXwNRO
	WIsf3RwxM8r0RKceaY9fAXuoHbKFM5YoVhKOyjEhpumY8l2Zcky6fxzZCXY3GE=
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=-1.9 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=laptop, H*r:sk:s17-v6s, H*c:alternative
X-HELO: mail-vk0-f42.google.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=gmail.com; s=20161025;        h=mime-version:in-reply-to:references:from:date:message-id:subject:to;        bh=SfRn36TGfgdLai1PQng1EWNDYezIlt/0d8T9mkdzuJA=;        b=h6NmnMoolG8KqRBZ+XlkkDtZXhzNo4iWG7KkUUYF5HSuep1QBQWS204zzphyLZxtBK         Xr3wI4YCEcslVhB5P1twgqKpYBgO+EdXDUJP5WuRPEF/I13O8p7tKS1ZJwininEA2bAH         pnOLXWZ8m8253RTe7s9gLxpEr93TjCI68xhB5K55t/wBbmG+iHuM1OW+rQFKjQAAlzxD         8uVwdr4mUN/R57wf7JA+BN/VjpIkQTCL5LMB6AoRnNRy5nHXfBMN94SZgq+6KRNA+vwR         8TeJdjrBUT4If2YeluMXxGyAfp3KVZXWwvGERxiRgRpSzdoQI/U1XQrJzJT2Tpsb9Qz+         7S+w==
MIME-Version: 1.0
In-Reply-To: <CAA5t8VoBPcSK8cHc+xuea-LREfV5f-H0qj034EvmzavbYCguJQ@mail.gmail.com>
References: <CAA5t8VqgNm+-wGn+iF-LtXUoFKL9+m=zH4=A959B0YsMGEqVmw AT mail DOT gmail DOT com> <6646b33b-ed7f-1078-6754-12259bf094e7 AT towo DOT net> <CAA5t8VoBPcSK8cHc+xuea-LREfV5f-H0qj034EvmzavbYCguJQ AT mail DOT gmail DOT com>
From: David Karr <davidmichaelkarr AT gmail DOT com>
Date: Tue, 31 Jul 2018 13:34:30 -0700
Message-ID: <CAA5t8Vpezn7qy-rnLPyn0Xb33ybUR2oGzHRfQT7+_3SjzH0bDQ@mail.gmail.com>
Subject: Re: 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"
X-IsSubscribed: yes

And I note that I tried running the same script from a Linux VM on my
laptop, and it doesn't have this symptom, so it does seem to have something
to do with Cygwin or Windows.

On Tue, Jul 31, 2018 at 1:15 PM, David Karr <davidmichaelkarr AT gmail DOT com>
wrote:

> On Tue, Jul 31, 2018 at 9:27 AM, Thomas Wolff <towo AT towo DOT net> wrote:
>
>> 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...
>>
>
> I hope this isn't it.  This is really the only issue I have with running
> kubectl in Cygwin.  It takes and outputs text perfectly fine.  I use pipes
> for input and output with no issues.  When I run kubectl with winpty, it
> changes the text encoding in ways I don't understand yet.
>
>
>
>>
>> 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).
>>
>
> I guess that makes sense. It appears to be irrelevant to my problem.
>
>

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