-
Notifications
You must be signed in to change notification settings - Fork 320
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running Azurite with custom port using docker compose #2384
Comments
Hi @wayne-w-cloud , With 400 error returned, seems you have successfully connected to Azurite, which means customized port should not be the root cause for the error. Could you share Azurite's debug log? With the log, we'd be able to see why the 400 happens. |
Here is my log. Thanks!
|
Can you enable debug log in Azurite? Following is a sample to let Azurite in docker output debug log to folder c:/azurite:/workspace:
You can see it map docker container's workspace to c:/azurite:/workspace, and output debug log to workspace folder. |
No response from customer for several months. Close this issue for now, any further investigation needed, please feel free to reopen the issue. |
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 hub
What's the Node.js version?
What problem was encountered?
I am trying to run azurite with azure function python using custom port via docker compose. I was able to use the custom port to start the azurite and having storage explorer connect to it. I am having issue to start the function.
Steps to reproduce the issue?
My docker compose file looks like
My connection string is
If possible, please provide the debug log using the -d parameter, replacing <pathtodebuglog> with an appropriate path for your OS, or review the instructions for docker containers:
Please be sure to remove any PII or sensitive information before sharing!
The debug log will log raw request headers and bodies, so that we can replay these against Azurite using REST and create tests to validate resolution.
Have you found a mitigation/solution?
The text was updated successfully, but these errors were encountered: