I have two containers and they expose the same port. I want to run them in the same task as they are part of the same system. But I cannot do this with Fargate because there are no port mapping and the host port should be the same as container port for the awsvpc network mode (only supported by Fargate).
It's an essential feature of Docker and it's strange that it seems to be not supported by Fargate. Is there really no way to do this or I'm missing something?
Use application load balancer to your service and set your custom port in target group and host port should be set the same as container port. This is our tested solution.
The simplest way to solve this problem is to make the port of your Docker container configurable and then pass it to the container as an environment variable. Example:
Dockerfile
FROM python:3.10-slim-bullseye
ENV PORT 5000
# Do all your container setup
# ...
EXPOSE $PORT
ENTRYPOINT path/to/entrypoint.sh
In entrypoint.sh, you need to set the app itself to use the port provided in the PORT environment var.
Then in your task definition, set the port mapping to a different port per container and provide the port as an env var:
{
// ...
"portMappings": [
{
"hostPort": 5001,
"protocol": "tcp",
"containerPort": 5001
}
],
// ...
"environment": [
{
"name": "PORT",
"value": "5001"
},
]
}
If you don't override the port via an environment variable, it will use the default port declared in the Dockerfile (in this case, 5000).
I had a similar issue in asp.net and was able to resolve it by creating only one container and have webapplications in different folders.
From a docker file my entry point is a powershell script.
FROM mcr.microsoft.com/dotnet/framework/aspnet:4.8-windowsservercore-ltsc2019 AS final
EXPOSE 80
WORKDIR /aspnet-startup
COPY Startup.ps1 .
WORKDIR /inetpub/wwwroot
COPY Web1 ./Web1
COPY Web2 ./Web2
ENTRYPOINT ["powershell.exe", "c:\\aspnet-startup\\Startup.ps1"]
Inside the Startup.ps1, I created an app pool and a web application.
# Create WebApp Pool
New-WebAppPool -Name "Web1"
New-WebAppPool -Name "Web2"
# Create WebApplication
New-WebApplication -Name "Web1" -Site "Default Web Site" -PhysicalPath "C:\inetpub\wwwroot\Web1" -ApplicationPool "Web1"
New-WebApplication -Name "Web2" -Site "Default Web Site" -PhysicalPath "C:\inetpub\wwwroot\Web2" -ApplicationPool "Web2"
C:\ServiceMonitor.exe w3svc
You will have to switch to ec2 based ecs instead of fargate. Also you can run on different port and use service discovery feature in fargate to communicate each other. Might need code changes.
