You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is done. Leaving the issue open until it is documented.
With CTP 3, I was able to get a container started with a flancy server serving pages publicly. However, a couple of things to note
when you use netsh in a container to set http urlacl, you see the results in the parent, not the container. However, it does work. It also works fine if your admin and just use the -public switch.
There are no errors given in the container. Hopefully this is fixed with ctp 4. It makes troubleshooting impossible
Need to include or think about routing recipe. The internal ips need to be reachable from outside of the host. Perhaps the vswitch should be a passthrough and then I can just give it a unique IP. Either way, this has to be included in the recipe/documentation
Need to figure the way to get a script to launch at container launch. Right now I am entering a pssession and launching manually.
The text was updated successfully, but these errors were encountered:
Got it to work with a NAT pretty easily
add-windowsfeature routing
netsh interface portproxy add v4tov4 listenport=8888 connectaddress=172.16.0.2 connectport=8000 protocol=tcp
However, leaving issue open until documentation is complete. Still need to get startup commands to work and share how to save flancy container images so they can be moved to other hosts.
This is done. Leaving the issue open until it is documented.
With CTP 3, I was able to get a container started with a flancy server serving pages publicly. However, a couple of things to note
Need to figure the way to get a script to launch at container launch. Right now I am entering a pssession and launching manually.
The text was updated successfully, but these errors were encountered: