UDP port expose cannot be configured from VIC HTTP interface.

[stuclem]

@Hedgehog57 commented on Tue Oct 01 2019

Summary

UDP port expose cannot be configured from VIC HTTP interface.

Environment information

vSphere and vCenter Server version

VSphere 6.7U3
ESXi 6.7U3
VCenter VCSA 6.7U3

VIC version

1.5.4

VCH configuration

vic-machine-windows.exe create --target vcenter --user username@domain --compute-resource vm-cluster --image-store esxi-store --volume-store esxi-store/vch1-name-volumes:default --name vch1-name --public-network network --containers 20 -b vch1-bridge --no-tlsverify --registry-ca ca-v3.crt

Details

Steps to reproduce

open https://vic-host.domain:8282
authorize
Library ->Templates -> Create template ->Add container ->choose anything -> network -> port binding: /udp -> container number: udp ->save

Actual behavior

Edit container -> Network
port definitions are empty.

Expected behavior

ports must be saved with protocol. In the example I use UDP. Entering TCP leads to the same result. If no protocol is specified only TCP will be exposed.

Logs

After fixing issue #8573 on the VCH side everithing is OK. Creating container "by hand" from docker command line works fine.

See also

Troubleshooting attempted

• Searched GitHub for existing issues. (Mention any similar issues under "See also", above.)
• Searched the documentation for relevant troubleshooting guidance.
• Searched for a relevant VMware KB article.

---

@renmaosheng commented on Tue Oct 22 2019

I would suggest to use command line for UDP. we would not fix the UI. @yuyangbj we should document this, thanks.

---

@Hedgehog57 commented on Tue Oct 22 2019

Hello @renmaosheng

What kind of CLI? docker CLI? But it mean that developer must create dockerfile on its own computer. There will be no way to modify image on VIC. And no way to share templates.
As of me its a very common usage. If You need to create DNS server, DNS proxy on any other UDP-based container You need not to use VIC, but docker.

Or did I miss something?

---

@yuyangbj commented on Wed Feb 12 2020

@Hedgehog57 you can use the traditional docker CLI to specify protocol and expose port. I will document the UI cannot support it. Thanks.

---

@stuclem commented on Wed Feb 12 2020

Hi @VinodJIsaac can you please work with @yuyangbj to get this documented? Thanks!

[stuclem]

Moved to the vic-product repo for doc.

[fabiogermann]

Just FYI - there is a workaround for anyone that is looking for this. Create a template in VIC (in library/templates), export it as docker compose and change the section:

ports:
  - "6060:6060"

to:

ports:
  - "6060:6060/udp"

and re-import the template. The UDP port will be saved in the template and you can use it.