jhonnyff
commented
2 years ago thanks for the help, error for a bad port config, not config in program file C#, only Json file of configuration
Open jhonnyff opened 2 years ago
jhonnyff
commented
2 years ago thanks for the help, error for a bad port config, not config in program file C#, only Json file of configuration
docker-robott
commented
1 year ago There hasn't been any activity on this issue for a long time.
If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale comment.
If not, this issue will be closed in 30 days.
Prevent issues from auto-closing with a /lifecycle frozen comment.
/lifecycle stale
docker-robot[bot]
commented
1 year ago There hasn't been any activity on this issue for a long time.
If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale comment.
If not, this issue will be closed in 30 days.
Prevent issues from auto-closing with a /lifecycle frozen comment.
/lifecycle stale
Dear, please your help with this case Context: In Azure there are 2 subscription accounts, A and B. In subscription A, the “resource group” is configured where the “Container Registry” has been created. In subscription B, it is where the "Web service" must be created, taking the image of the "Container Registry" found in subscription A. Process 1 Step 1: The “Web service” image is created, it is created by a “dockerfile” file
Step 2: A "Web App" service is created through the Marketplace service, selecting "Web App", the service configuration is for a Linux server
It is also verified in the log that the extraction is carried out correctly
And at the end of the extraction, it indicates that it is calling port 80
Step 3: The call is made by "Postman", 503 is displayed as a result
When calling one of the services, it is evident that port 5004 is being called, this port is configured in the dockerfile
================================ Note 1: The same steps indicated in Process 1 were carried out, in subscription A (major), using an existing "resource group", when reviewing the log it shows me the same indicated in step 2 and 3
================================ Note 2: An azure account is created with a subscription, creating "resource group", for "Container Registry", another to create the "Web service" Step 1: The creation of a “Web service” image is carried out, it is created by a “dockerfile” file
Step 2: We proceed to create a "Web App" service through the Marketplace service, selecting Web App, the service configuration is for a Linux server
The websetting11 service is created, when calling the service for the first time, the configured port is identified in the log history, then the extraction of the image is indicated.
And at the end of the extraction, it indicates that it is calling port 80
Step 3: The call is made by Postman, resulting in 200 When reviewing the log, the call of port 5011 is identified, which has been configured in the dockerfile
When making the call by Postman, to a "Web service" method, resulting in "200", as shown in the image
Expected behavior
Actual behavior
Information
Steps to reproduce the behavior