Closed Arash-Sabet closed 7 months ago
@Arash-Sabet
Do you run test inside same docker image with Azurite, or outside the docker image which include Azurite?
For your reference, this is Azurite docker file, and it bind Azurite blobHost to 0.0.0.0 by default on docker image, and when start Azurite docker image need map 10000:10000 port to make sure the Azurite blob endpoint can be access outside of Azurite. See more details in https://github.com/Azure/Azurite?tab=readme-ov-file#run-azurite-v3-docker-image
@blueww The tests are run inside the docker image. So, should I use the IP address of 0.0.0.0 in the Xunit tests?
@Arash-Sabet
I might still need some time to investigate this issue. Would you please share the Azurite debug log which can help the investigation?
Besides that, could you also try to start Azurite with parameter: --blobHost 0.0.0.0 --queueHost 0.0.0.0 --tableHost 0.0.0.0
@Arash-Sabet
I might still need some time to investigate this issue. Would you please share the Azurite debug log which can help the investigation?
Besides that, could you also try to start Azurite with parameter: --blobHost 0.0.0.0 --queueHost 0.0.0.0 --tableHost 0.0.0.0
I cannot access the log information as the docker image is a part of a k8s cluster. I will try the azurite per your suggestion a bit later on but bottom line the issue per my description should not happen. @blueww
Running azurite on the IP address of 0.0.0.0
worked.
Good to the issue is resolved by running Azurite with host as 0.0.0.0 I will close this issue.
Feel free to contact us again if need any further assistance on Azurite.
Thanks for the help @blueww
Which service(blob, file, queue, table) does this issue concern?
All
Which version of the Azurite was used?
Presumably the latest version
Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)
npm
What's the Node.js version?
Presumably the latest version
What problem was encountered?
Azurite does not launch in a docker image as communication with it over port# 10000 shows connection failure
Steps to reproduce the issue?
We followed the steps outlined in this article to build a k8s Azure DevOps agent. We augmented the docker yaml file to include Azurite in the docker image to use its instance in our integration tests run by the build pipelines. The code snippet to include Azurite is per below:
All build steps of our C# solution pass successfully using this k8s-backed build agent. Unfortunately, we realize the following error message produced by our Xunit integration tests when running them in the Azure DevOps pipeline:
The only architectural difference between our image and the one produced by the aforementioned article is that we are using Ubuntu 22.04 instead of Ubuntu 20.04.
Have you found a mitigation/solution?
No