Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

ContainerPort not working

See original GitHub issue

Hi, I’m trying to specify a container port but it seems like props is not working properly and keep default back to 80

Received response status [FAILED] from custom resource. Message returned: InvalidPar
ameterException: The container sample-website did not have a container port 80 defined.

const taskDefinition = new DummyTaskDefinition(this, 'DummyTaskDefinition', {
      image: 'nginx',
      family: this.props.family,
      containerPort: 8080,
    });

Issue Analytics

State:
Created 2 years ago
Reactions:3
Comments:10 (4 by maintainers)

Top GitHub Comments

1reaction

fasatrixcommented, Jul 27, 2021

@hupe1980 Thanks for the new version of the package. it seems to have fixed the issues. This can no be closed

1reaction

fasatrixcommented, Jul 15, 2021

@hupe1980 did you have a chance to take a look? Alternatively do you have examples where you first instanciate the DummyTaskDefinition without port(defaults to 80) and then pass the real taskDef with a different image and port? I am very looking forward as the code that handles this part seems to be correct however it’s hard to say without tests and/or more examples. The behaviour mentioned by @cao2504 happens for me as well

Top Results From Across the Web

Unable to access exposed port on kubernetes - Stack Overflow

After that I created a kubernetes yaml to build the pod exposing only port 80. And the service along with it. But the...

Problem to get through to a container port - General Discussions

I have a problem with one of my Docker containers. It provides two web application services, RStudio Server and R Shiny Server.

I might have broken container port mapping - Server Fault

The VIRTUAL_PORT setting looks incorrect. You are using VIRTUAL_PORT=8001 while the container is listening on port 80.

AWS::ECS::TaskDefinition PortMapping - AWS CloudFormation

The PortMapping property specifies a port mapping. Port mappings allow containers to access ports on the host container instance to send or receive...

Connecting Applications with Services - Kubernetes

Create an nginx Pod, and note that it has a container port specification: ... This is the problem a Service solves. A Kubernetes...