ContainerPort not working
See original GitHub issueHi, 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 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...
Read more >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.
Read more >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.
Read more >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...
Read more >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...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@hupe1980 Thanks for the new version of the package. it seems to have fixed the issues. This can no be closed
@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