HostPort not present in ECS Task Metadata Endpoint response with bridge network type

[MartinMitro]

Summary

HostPort not present in ECS Task Metadata Endpoint response with bridge network type

Description

I have a Task with bridge network type. When executing

curl $ECS_CONTAINER_METADATA_URI_V4/task

I see that host port is missing in response, however I can find it when reading ECS_CONTAINER_METADATA_FILE

Expected Behavior

Host port is also present in Endpoint response

Observed Behavior

Host port is missing

Environment Details

ECS Agent version: 1.39.0

[mythri-garaga]

Could you please send the task definition(json file) to ecs-agent-external at amazon.com?

[sharanyad]

Thanks for the information @MartinMitro . This has been identified as a bug in agent where ports for metadata http response comes from

amazon-ecs-agent/agent/api/container/container.go

Line 143 in 3776bee

Ports []PortBinding `json:"portMappings"`

whereas for the metadata file, it comes from

amazon-ecs-agent/agent/api/container/container.go

Line 248 in 3776bee

KnownPortBindingsUnsafe []PortBinding `json:"KnownPortBindings"`

We will work on fixing this.

[cyastella]

This is fixed in agent 1.41.1 Please update to latest version, and if you still find issue let us know. Thanks.