Hello Josh Majors,
Welcome to the Microsoft Q&A and thank you for posting your questions here.
I understand that you're experiencing port mapping issues with your Azure ML.
Since you are using Custom Application feature, which automates deployment. Kindly understand that Azure ML’s UI does not always bind ports correctly, requiring manual NSG/Docker configuration.
- Add NSG rules for custom ports specified in the UI. Manually add an inbound rule: Protocol: TCP Source Port: * Destination Port: 2222 Action: Allow Check this out: https://learn.microsoft.com/en-us/azure/virtual-network/manage-network-security-group#create-security-rules
- Run the bash command to verify the Docker Port Binding SSH into the VM:
If the output does not showdocker ps --format "table {{.ID}}\t{{.Names}}\t{{.Ports}}"
0.0.0.0:2222->22/tcp
, Azure ML failed to map the ports correctly. This is a known UI bug. Let me know and this is a workaround. However, - Your Docker container’s application should be listening on port 22. If your app uses a different port such as 80, update the target port in the Azure portal to match: Target Port: 80 (container port), Published Port: 2222 (host port) and disable conflicting services and ports.
- Use Azure ML’s Managed Endpoints (Best Practice) will be a great gain.
I hope this is helpful! Do not hesitate to let me know if you have any other questions or clarifications.
Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.