Deploying Docker Container of .NET Application through App2Container

Question

I have a .NET 4.8 application that runs successfully on an EC2 instance. It uses IIS and the application is accessible via a website. It connects to a SQL Server Express database running on RDS to retrieve credentials for users to login.

I am using App2Container to containerize this application. From the Docker image it creates, I am able to access the website locally (on the EC2 instance that I am testing on). However, my container is not able to access the RDS. In general, my container is not able to access any websites. This was confirmed through performing a ping on different websites. This is the response I am getting:

ping google.com
Ping request could not find host google.com. Please check the name and try again.

This led me to believe that there are issues with the DNS of the Docker container. However, I added the same DNS server that my EC2 instance uses, but this issue persists.

I am not sure why I cannot connect to my RDS database.

re:Post Agent · Answer

The issue you're experiencing with your containerized .NET application not being able to access external resources, including your RDS database, is likely related to networking configuration rather than DNS issues specifically.

When using App2Container to containerize your .NET application, there are a few things to consider:

1. Network Mode: By default, containers use bridge networking, which can limit their ability to communicate with external resources. You may need to configure the container to use host networking or create a custom network that allows external communication.

2. Security Groups: Ensure that the security group associated with your container allows outbound traffic to your RDS instance and other required resources.

3. VPC Configuration: Make sure your container is running in the same VPC as your RDS instance, or that proper VPC peering is set up if they're in different VPCs.

4. Connection String: Verify that the connection string in your containerized application is correctly pointing to the RDS endpoint.

5. Firewall Settings: Check if there are any firewall settings within the container or at the host level that might be blocking outbound connections.

To resolve this issue:

1. Review the network settings in your App2Container configuration (deployment.json file) to ensure proper network access is granted to the container.

2. Check the task definition generated by App2Container and make sure it includes the necessary network configuration.

3. When deploying to Amazon ECS, ensure that the task is launched in the correct VPC and subnet with appropriate security group settings.

4. Consider using AWS VPC endpoints for services like RDS to improve security and reduce latency.

5. If the issue persists, you may need to manually adjust the Dockerfile or container runtime settings to ensure proper network configuration.

Remember that containerizing an application can sometimes require additional configuration to maintain the same connectivity as the original non-containerized version. It's important to carefully review and adjust network settings throughout the containerization and deployment process.  
**Sources**  
[Deploy application containers to Amazon Elastic Container Service with AWS App2Container - AWS App2Container](https://docs.aws.amazon.com/app2container/latest/UserGuide/a2c-integrations-ecs.html)  
[Containerization - Replatform .NET Applications with Windows Containers](https://docs.aws.amazon.com/whitepapers/latest/replatform-dotnet-apps-with-windows-containers/containerization.html)  
[AWS App2Container Features | Containerize Applications | Amazon Web Services](https://aws.amazon.com/app2container/features/)

Deploying Docker Container of .NET Application through App2Container

Relevant content