Azure / Azure/Azurite

errors using --loose in docker-compose

Open
#381 5 comments 0 reactions 1 assignee Claimed by @Poku8 View on GitHub
docker enhancement good first feature NewArch question
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?
latest

### Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)
docker pull mcr.microsoft.com/azure-storage/azurite

### What's the Node.js version?

### What problem was encountered?
When trying to run with --loose I get an error.

docker-compose.yml
azure_storage_emulator:
container_name: azurite
image: mcr.microsoft.com/azure-storage/azurite:latest
restart: always
command: "--loose"
ports:
- "10001:10001"
- "10000:10000"

I get this error:

Creating azurite ... error
ERROR: for azurite Cannot start service azure_storage_emulator: b'OCI runtime create failed: container_linux.go:346: starting container process caused "exec: \\"--loose\\": executable file not found in $PATH": unknown'

ERROR: for azure_storage_emulator Cannot start service azure_storage_emulator: b'OCI runtime create failed: container_linux.go:346: starting container process caused "exec: \\"--loose\\": executable file not found in $PATH": unknown'
ERROR: Encountered errors while bringing up the project.

### Steps to reproduce the issue?

run above using
docker-compose up

### Have you found a mitigation/solution?
no. just to not use --loose . but then i get errors in my service that say to use --loose.

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.