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=pA1+IWL
	ZNxHfbyaNOJP6U7oSJRDiYtnqa2j1qCMjhg+ejsNtyV6+cjdLAwAvB2XXDuJJ1R0
	zN6DCgPANb1tBGIHYRwtJ9qS00w1QM/qg28AsPcJzKA6WN5eM2HUgS4uiRqRHTxn
	1/iQ9qdyhaA1rgqcFIRL9Zdumx9umYwX7DDU=
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=wVYnS0eUjA8BD
	gvaxnJ3oX0tT3U=; b=o7/JUvxGqifgT/7fTYbwsS0QtRnaq3yE9D8elIY/02rp4
	2ber7/n/1wHZsQ84wJ5ITxOBspnnO1ISM2kNrrrDvQVPn8pabM5kJi7U3ra0V8RL
	2wdinhtzTv40Y4i7o75Y+lsVh9dJUjY76yTjrLNs9ob+islO0OTIfcvKAcJpis=
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=pipes, 31072018, 31.07.2018, H*c:alternative
X-HELO: mail-ua0-f169.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=2PxJXAEz2FMBM+e53t9LVjajwUroKKBf9rlBAMm7ETw=;        b=RJXrS9dBVJ54ZnZddnfSjVzdJtmdNFIXW75gmGgoYCix2TEgH6gTkyO4/x1iZ0paxs         a0FG86qrk7e+XFJgnH1My3Wahu+kWRFatpB7/eJS70XNXOK64BilN6PWWXVLc6Qud08a         1Wj2OP2UwC+dbCWcArtJWu1hekrl/lW+b4L3+3wRDB/rlMtzMYTGf2qxp65bXM6d1wR5         tX4/xrjI4PMmRSq7O1L1Qmz/a5mU6s3LyBZa1c3wX8asL66zOPQWoDWhL1SeIA3L94ZC         2eW13WPE64MEmUOqhZnER9e3uPfmF28sq1Svs9j75ZebSVsrUjYCD4mut1xbxAnOGxdf         UfVg==
MIME-Version: 1.0
In-Reply-To: <6646b33b-ed7f-1078-6754-12259bf094e7@towo.net>
References: <CAA5t8VqgNm+-wGn+iF-LtXUoFKL9+m=zH4=A959B0YsMGEqVmw AT mail DOT gmail DOT com> <6646b33b-ed7f-1078-6754-12259bf094e7 AT towo DOT net>
From: David Karr <davidmichaelkarr AT gmail DOT com>
Date: Tue, 31 Jul 2018 13:15:36 -0700
Message-ID: <CAA5t8VoBPcSK8cHc+xuea-LREfV5f-H0qj034EvmzavbYCguJQ@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

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