Closed szikk closed 2 years ago
If this is a non aks/aks-engine enviroment, you may need to add a postrouting rule to the vm
Hello @matmerr the route was already added but I still did not have internet access from container and also the host vm did not have any connectivity to the container but other VM from inside vnet had. (I also disabled all the NSGs from vnet)
I might be getting a little bit confused here and I think is better to tell you the end goal. Basically I am trying to create Docker containers withing Azure VNET and with a Standard SLB balance traffic between them.
I tried to follow the instruction from here: https://docs.microsoft.com/en-us/azure/virtual-network/deploy-container-networking#deploy-plug-in-for-docker-containers
I also tried this approach: https://github.com/Azure/azure-container-networking/blob/master/docs/cnm.md but I ended up in the same place.
What would be the correct approach for this?
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days
Issue closed due to inactivity.
What happened:
I've setup an nginx server to run in a container with CNI. The container is accessible via ICMP but TCP traffic is now flowing towards the container ends up with Connection refused. Outbound traffic is also not available.
What you expected to happen:
Be able to access the container application via the VNET IP
How to reproduce it:
Orchestrator and Version (e.g. Kubernetes, Docker):
Docker version 19.03.12, build 48a66213fe
Operating System (Linux/Windows):
Linux
Kernel (e.g.
uanme -a
for Linux or$(Get-ItemProperty -Path "C:\windows\system32\hal.dll").VersionInfo.FileVersion
for Windows): 18.04.1-Ubuntu SMP Mon Jul 13 12:54:45 UTC 2020 x86_64 x86_64 x86_64 GNU/LinuxAnything else we need to know?:
cat /var/log/azure-vnet.log:
cat /var/log/azure-vnet-ipam.log: