Azurite connection refused by storage explorer when running through a docker-compose file

[sambowenhughes]

Which service(blob, file, queue, table) does this issue concern?

Blob

Which version of the Azurite was used?

3.7.0

Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)

DockerHub

What's the Node.js version?

N/A

What problem was encountered?

When running azurite through a docker-compose file it seems to run perfectly fine.

Following output: azurite_1 | Azurite Blob service is starting at http://0.0.0.0:10000 azurite_1 | Azurite Blob service is successfully listening at http://0.0.0.0:10000

However when I then go to view the emulated storage account through Azure Storage Explorer I get the following error:

Unable to retrieve child resources.

Details: connect ECONNREFUSED 127.0.0.1:10000

This however does not cause an issue when running the Azurite in the following way: docker run -p 10000:10000 -p 10001:10001 mcr.microsoft.com/azure-storage/azurite

Steps to reproduce the issue?

1. Create your docker-compose.yml file.
2. Add the following:

azurite: image: mcr.microsoft.com/azure-storage/azurite hostname: azurite ports:

• "1000:1000"
• "1001:1001"

3. Run docker-compose up
4. Open up Azure Storage Explorer
5. Inspect Blob Containers by selecting the dropdown

Have you found a mitigation/solution?

Nope - unsure however whether this is an issue to do with Azurite or Storage Explorer.

[blueww]

@sambowenhughes

As docker works, this seems not an Azurite issue.

We have an issue on docker-compose before, and it looks like works in docker-compose. You might can refer to it. https://github.com/Azure/Azurite/issues/381

[feluelle]

You mapped the wrong ports.

- "1000:1000"
- "1001:1001"

It should be:

+ "10000:10000"
+ "10001:10001"

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.