starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

docker-machine ssh shows raw escape code buffer in cmd #499

New Issue
Closed
opened 2026-01-30 21:53:47 +00:00 by claunia · 3 comments
claunia commented 2026-01-30 21:53:47 +00:00
Owner
Copy Link

Originally created by @Biswa96 on GitHub (Dec 30, 2018).

*Windows build number: Version 10.0.18305.1000]

  • Command used: docker-machine.exe ssh docker-host which uses Go-lang implementation of ssh in docker-machine.exe.

  • What's wrong / what should be happening instead:

    • In CMD:

cmd-docker-ssh

  • In WSL:

wsl-docker-ssh

I don't know if this is by-design or not. Or may be I should use terminal or not. If you need more information just ask.

Originally created by @Biswa96 on GitHub (Dec 30, 2018). *Windows build number: Version 10.0.18305.1000] * Command used: `docker-machine.exe ssh docker-host` which uses Go-lang implementation of `ssh` in `docker-machine.exe`. * What's wrong / what should be happening instead: - In CMD: ![cmd-docker-ssh](https://user-images.githubusercontent.com/31443074/50550013-c5cd5100-0c8d-11e9-8463-cb1923be5940.PNG) - In WSL: ![wsl-docker-ssh](https://user-images.githubusercontent.com/31443074/50550015-ce258c00-0c8d-11e9-8ef1-d68a4a0c6436.PNG) I don't know if this is _by-design_ or not. Or may be I should use terminal or not. If you need more information just ask.
claunia commented 2026-01-30 21:53:48 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Dec 30, 2018):

It looks like docker-machine is not setting ENABLE_VIRTUAL_TERMINAL_PROCESSING on the console output handle. That'd be a good issue to raise on either docker-machine or the Go library they're using for terminal output.

WSL ssh works, of course, because WSL sets ENABLE_VIRTUAL_TERMINAL_PROCESSING.

@DHowett-MSFT commented on GitHub (Dec 30, 2018): It looks like `docker-machine` is not setting `ENABLE_VIRTUAL_TERMINAL_PROCESSING` on the console output handle. That'd be a good issue to raise on either docker-machine or the Go library they're using for terminal output. WSL ssh works, of course, because WSL sets `ENABLE_VIRTUAL_TERMINAL_PROCESSING`.
claunia commented 2026-01-30 21:53:48 +00:00
Author
Owner
Copy Link

@Biswa96 commented on GitHub (Dec 31, 2018):

@DHowett-MSFT Found another question. Is this in same category of mine?

@Biswa96 commented on GitHub (Dec 31, 2018): @DHowett-MSFT Found another [question](https://superuser.com/q/1386570/726810). Is this in same category of mine?
claunia commented 2026-01-30 21:53:48 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Dec 31, 2018):

That one doesn't seem related, actually. It is lacking some reasonably critical info, mostly surrounding which versions of which tools are in use, whether the person is using Linux docker against a Windows host, whether this is Python for Windows in docker or Python for Linux, and so on.

@DHowett-MSFT commented on GitHub (Dec 31, 2018): That one doesn't seem related, actually. It _is_ lacking some reasonably critical info, mostly surrounding which versions of which tools are in use, whether the person is using Linux docker against a Windows host, whether this is Python for Windows in docker or Python for Linux, and so on.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#499
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?