When using vagrant within a warp terminal session a vagrant up never completes. The VM will get to the provisioning stage and then timeout during provisioning.
Running the same vagrant up script within the standard macOS terminal app works perfectly every time.
An example error message
==> default: Running provisioner: choco (shell)...
default: Running: inline PowerShell script
An error occurred executing a remote WinRM command.
Shell: Elevated
Command: powershell -ExecutionPolicy Bypass -OutputFormat Text -file "C:\tmp\vagrant-shell.ps1"
Message: HTTPClient::KeepAliveDisconnected: Connection reset by peer @ io_fillbuf - fd:13
To Reproduce
Vagrant up of a Windows 11 VM and provision with a few applications.
Sorry about this @WizBangCrash Thanks for reporting. I think this is the first report of this. Will send updates once there are some, no ETA on when that'll be however.
Discord username (optional)
No response
Describe the bug
When using vagrant within a warp terminal session a
vagrant up
never completes. The VM will get to the provisioning stage and then timeout during provisioning.Running the same vagrant up script within the standard macOS terminal app works perfectly every time.
An example error message
To Reproduce
Vagrant up of a Windows 11 VM and provision with a few applications.
Example Vagrantfile to cause the timeout:
Expected behaviour
Vagrant up should run to completion.
Screenshots
No response
Operating System
MacOS
OS Version
13.0.1
Shell Version
zsh 5.8.1 (x86_64-apple-darwin22.0)
Warp Version
0.2022.11.01.08.03.stable_00
Additional context
I'm running on a MacBook Pro 2.6 GHz 6-Core Intel Core i7 with 32GByte RAM
Does this block you from using Warp daily?
Yes
Warp Internal (ignore): linear-label:b8107fdf-ba31-488d-b103-d271c89cac3e
No response