This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(163.2, 72%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELS%3C/text%3E%3C/svg%3E)
How can we access multiple private repositories in docker-compose file?
We have to work with 4 different images from different private repositories, and looks like this is not supported yet. When is the ETA for this feature?
Currently @Logeeswaran, Saranya (Cognizant) , there are no plans for docker compose beyond what's available. The team is evaluating options for scenarios such as this, but nothing planned. No ETA to share at the moment.
Thanks for the answer.
I am actually able to access all 4 images with Docker-compose.
But problem is one image is not serving the other one's request.
UI is exposed via the port 8080. When it receives incoming requests, it has to be served by another port 5005.
The container running in 5005 is not serving this request.
How can we fix the communication between the containers?
Containers in docker-compose are visible to each other right?
Can you clarify...
But problem is one image is not serving the other one's request.
UI is exposed via the port 8080. When it receives incoming requests, it has to be served by another port 5005.
Containers can see each other but only one image, your UI in this case, will respond to external requests. Is your UI not able to call this backend service?
Yes. 5005, though running is not serving the UI.
I gave the endpoint for 5005 as <appname>.azurewebsites.net:5005/webhook
I did check exposing ONLY <appname>.azurewebsites.net:5005/webhook and it was up and running.
So images when running in isolation is fine.
Looks like containers are not able to communicate with each other.
You won't be able to refer to the other service via .azurewebsites.net:5005. Only the image bound to port 80 is exposed. If you want your UI to communicate with the other service, you should reach that service by the service name you defined it as in your docker compose yaml file. See https://learn.microsoft.com/en-us/azure/app-service/tutorial-multi-container-app#download-the-sample for an example.
Yes Ryan. I am accessing them by service name WITHIN the application.
However, this particular UI is a chatroom with embedded HTML below -
window.chatroom = new window.Chatroom({
title: "chatroom",
container: document.querySelector(".chat-container"),
welcomeMessage: "Hi there",
host: "https://<app-name>.azurewebsites.net:5005",
speechRecognition: "en-US",
voiceLang: "en-US"
host is the container running the port 5005. If I refer it by service name, it is not recognizing.
So how to mention these container endpoints outside of the Azure app?
Remember @Logeeswaran, Saranya (Cognizant) , HTTP traffic is bound to the exposed port on your docker image and only HTTP/S are exposed to the public through the app service. So even though your UI is exposing 5005 at the container level, app service is sending port 80 traffic to 5005. If the UI image is handling the requests for Chatroom object, then drop the port from the endpoint.