Azure / Azure/Azurite

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

Open
#457 3 comments 3 reactions 1 assignee Claimed by @blueww View on GitHub
NewArch question stale
Dominant language
TypeScript
Stars
2.3k
Forks
393
Avg merge
1d 20h
Merged PRs (30d)
36

Description

### 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.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.