It's actually a clash with bash's command history and emacs. I opened T245898.
> On Feb 21, 2020, at 7:14 PM, Brooke Storm <[email protected]> wrote: > > I get what you mean now. This is a container launched by Kubernetes with the > webservice wrapper on a daemon in the cluster, so I don't consider it likely > that passing that through to the docker daemon would be possible. Configuring > docker to work differently across the fleet is more likely (which we could > consider if you open a Phabricator task for it). I've never used the key > combo to detach from a container, so I'd not encountered that issue. > Overall, I'm getting that this is a clash with tmux keybindings, right? > > On a task, we can poke at the issue a bit, and maybe record a solution, > either local to your tool account or in general. > > On 2/21/20 3:19 PM, Roy Smith wrote: >> Hmmm, yeah, I get the desire to keep production containers as minimal as >> possible. I had asked a while ago if it was possible to get Python 3.7 on >> the bastion hosts, but was told that's not feasible because of the way the >> distros are packaged. So, I seem to be stuck with having to flip back and >> forth between two hosts, which is a really awkward way to work. >> >> As for the control-p issue, I believe the behavior I'm seeing is described >> in this stack overflow article >> <https://stackoverflow.com/questions/41820108/ctrl-p-and-ctrl-n-behaving-unexpectedly-under-docker>. >> But that describes a fix using docker commands, and I haven't figured out >> how to map that to the webservice wrapper. To answer your question, though, >> my connection stack is: >> >> Terminal window on MacOS >> ssh -t dev.tools.wmflabs.org <http://dev.tools.wmflabs.org/> tmux new -As >> spi-tools-dev >> become spi-tools-dev >> webservice --backend=kubernetes python3.7 shell >> >> >>> On Feb 21, 2020, at 12:35 PM, Brooke Storm <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> Hello Roy, >>> The container environment for webservice shell is the same image as the >>> runtime containers for a service, so I'd rather not support ssh in the >>> containers because they need to be light-weight, limited and including that >>> would raise some interesting security issues in the cluster otherwise. The >>> workflow does need some work, though, and we are experimenting with ways to >>> make it more sensible. >>> >>> On the CTRL-P issue, I'm not entirely sure what you mean and might need >>> more information about your setup. That usually is dictated by the shell >>> you are using rather than anything to do with Kubernetes. In some shells, I >>> know you need to use SHIFT-CTRL-P. I have no issues on my Mac. What client >>> are you using the connect via SSH? I might be able to recreate the issue >>> and figure out a fix. >>> -- >>> Brooke Storm >>> SRE >>> Wikimedia Cloud Services >>> [email protected] <mailto:[email protected]> >>> IRC: bstorm_ >>> >>> >>> On 2/21/20 7:40 AM, Roy Smith wrote: >>>> The bastion hosts don't have python3.7, and the k8s hosts don't have ssh, >>>> so "git pull" and "git push" don't work. Which means I need to keep >>>> flipping back and forth between the two during development. Is there some >>>> way to get ssh working on the k8s hosts, so I can do everything in one >>>> place? >>>> >>>> The other annoyance is that when you connect with "webservice >>>> --backend=kubernetes python3.7 shell", the connection eats control-p's Is >>>> there some way to turn that off, or at least reconfigure it to use a >>>> different command character? >>>> _______________________________________________ >>>> Wikimedia Cloud Services mailing list >>>> [email protected] <mailto:[email protected]> (formerly >>>> [email protected] <mailto:[email protected]>) >>>> https://lists.wikimedia.org/mailman/listinfo/cloud >>>> <https://lists.wikimedia.org/mailman/listinfo/cloud> >>> _______________________________________________ >>> Wikimedia Cloud Services mailing list >>> [email protected] <mailto:[email protected]> (formerly >>> [email protected] <mailto:[email protected]>) >>> https://lists.wikimedia.org/mailman/listinfo/cloud >>> <https://lists.wikimedia.org/mailman/listinfo/cloud> >> >> >> _______________________________________________ >> Wikimedia Cloud Services mailing list >> [email protected] <mailto:[email protected]> (formerly >> [email protected] <mailto:[email protected]>) >> https://lists.wikimedia.org/mailman/listinfo/cloud >> <https://lists.wikimedia.org/mailman/listinfo/cloud> > -- > Brooke Storm > SRE > Wikimedia Cloud Services > [email protected] <mailto:[email protected]> > IRC: bstorm_ > _______________________________________________ > Wikimedia Cloud Services mailing list > [email protected] (formerly [email protected]) > https://lists.wikimedia.org/mailman/listinfo/cloud
_______________________________________________ Wikimedia Cloud Services mailing list [email protected] (formerly [email protected]) https://lists.wikimedia.org/mailman/listinfo/cloud
