-
Notifications
You must be signed in to change notification settings - Fork 23
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
Edit network port forward rules #81
Comments
Hi! When last I looked into the OVF files exported from VirtualBox, the XML that you're referencing above was encapsulated in the VirtualBox-specific I've tried to keep COT agnostic of the various vendor-specific extensions of the specification so far, but if you can specify the exact functionality that you'd like to have here for processing a VirtualBox-specific OVF, I'm willing to consider adding it - i.e., what information would you like to appear in Thanks! |
If it helps at all, here's what it looks like when exported as OVF v2, with the hostip and guestip set.
|
I ended up finding a way around this -- I ran a docker container with virtualbox, imported the file, used VBoxManage to tweak the vm, and exported it. Feel free to close this ticket if you're not interested in implementing this anymore, thank your for considering it in the first place! |
Hello!
I'd like to be able to manipulate port forwarding rules on an OVF I have. However, I don't see a way to do it through
cot
, is this something that can be added? Or is there already a way to do it? The forward doesn't show up incot info
.This can be accomplished with
VBoxManage
, but the system I'm running the build on doesn't have virtualbox installed, and there doesn't appear to be a direct download for just the manage utility.When I export an OVA with forwarded ports on virtualbox, the network area looks something like this:
The text was updated successfully, but these errors were encountered: