Is it possible to have the same container port exposed as TCP and UDP?

[paulomorgado]

I'm trying to get this:

docker run -d -p 3478:3478 -p 3478:3478/udp -p 5349:5349 -p 5349:5349/udp -p 49152-65535:49152-65535/udp coturn/coturn

https://hub.docker.com/r/coturn/coturn

[sebastienros]

I was able to get close with this sample:

#pragma warning disable ASPIREPROXYENDPOINTS001 // Type is for evaluation purposes only and is subject to change or removal in future updates. Suppress this diagnostic to proceed.
builder.AddContainer("coturn", "coturn/coturn", "latest")
       .WithEndpoint("tcp1", e => { e.Port = 3478; e.TargetPort = 3478; e.Protocol = System.Net.Sockets.ProtocolType.Tcp; })
       .WithEndpoint("tcp2", e => { e.Port = 5349; e.TargetPort = 5349; e.Protocol = System.Net.Sockets.ProtocolType.Tcp; })
       .WithEndpoint("udp1", e => { e.Port = 3478; e.TargetPort = 3478; e.Protocol = System.Net.Sockets.ProtocolType.Udp; })
       .WithEndpoint("udp3", e => { e.Port = 5349; e.TargetPort = 5349; e.Protocol = System.Net.Sockets.ProtocolType.Udp; })
       .WithEndpointProxySupport(false);
#pragma warning restore ASPIREPROXYENDPOINTS001 // Type is for evaluation purposes only and is subject to change or removal in future updates. Suppress this diagnostic to proceed.

Currently trying to improve the API for this scenario, there is another WithEndpoint method that is very close but missing the protocol argument.

Also wondering how the port ranges could be provided.

Update: #7700

This would allow for: .WithEndpoint(port: 5349; targetPort: 5349; isProxied: false, protocol: ProtocolType.Udp)

[paulomorgado]

Thanks, @sebastienros.

Is this something from Aspire 9.1? I couldn't find WithEndpointProxySupport.

Without WithEndpointProxySupport, I got this:

Name	Value
tcp1	tcp://localhost:3478
tcp1 target port	tcp://127.0.0.1:45005
tcp2	tcp://localhost:5349
tcp2 target port	tcp://127.0.0.1:35683
udp1	tcp://localhost:3478
udp1 target port	tcp://127.0.0.1:39553
udp3	tcp://localhost:5349
udp3 target port	tcp://127.0.0.1:35683

tcp:// looks odd for UDP.

I'm still starting with this, but that port range might need to be exposed on the same ports as the internal container port and not proxied.

I wonder if I could achieve this as direct container commands. - UPDATE: .WithContainerRuntimeArgs("--publish", "65500-65535:65500-65535/udp") seems to work.

[sebastienros]

I confirm this is the behavior on docker, and if you provide a non-matching number of ports then you get:

PS > docker run -p 3478-3480:3478-3481/udp  coturn/coturn
docker: invalid ranges specified for container and host Ports: 3478-3481 and 3478-3480.
See 'docker run --help'.

[sebastienros]

Is that the same as EndpointAnnotation.IsProxied

Yes, for the whole container though.

[paulomorgado]

PS > docker run -p 3478-3480:3478-3481/udp  coturn/coturn
docker: invalid ranges specified for container and host Ports: 3478-3481 and 3478-3480.
See 'docker run --help'.

Not an expert, but, could it be because the ranges don't have the same size? Or the host ports are already being used?

Why can't I have dynamic ports when it's not proxied?

[sebastienros]

it be because the ranges don't have the same size

That was my point to show the error and that it is mapping things 1 to 1.

Why can't I have dynamic ports when it's not proxied?

You can, from docker directly, but the resources won't be able to know about them. What I meant was that DCP gives you random ports on startup. So if you define a target port I assume you don't want the proxy to kick in.

[paulomorgado]

For containers, DCP doesn't need to do that, because the container APIs inform what are the host ports for each published port.