New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
forwarded_port feature with SSH tunneling does not work #1439
Comments
Please update the version of vagrant-libvirt being used, 0.0.45 was release in 2018 and there has been a lot of work done on improving the forwarding behaviour. Try retesting with 0.7.0 |
I am not sure if this is the same issue, but it is similar. Running 0.7.0, the port forwarding works if a vagrant command is running. For instance, if I have a 5 VM cluster and I run |
It's likely that port forwarding using the docker container would need to leave the container running as docker stopping will terminate and child processes started from within the container. No way around that. I can't reproduce with a native install though and that would be different to this issue anyway as this is a out some failure to connect the forwarded port by the background ssh process that is running while you are saying it doesn't remain running at all |
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further. |
Hello,
I have been using
vagrant-libvirt
for 2 years without issue. Recently, I wanted to useforwarded_port
feature. In the backend it uses SSH, but I had no chance to make it work. When I reachlocalhost:3000
, I get a log file that only shows multiple of this lineI use Vagrant 2.2.3 with
vagrant-libvirt
0.0.45 on Debian Buster. CurrentVagrantfile
what is created aftervagrant init
with removing comment line of theforewarded_port
.The text was updated successfully, but these errors were encountered: