Neither Microsoft azurite nor ArangoDB would launch or become available within docker

Open
#430 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
azure, docker, node.js
Domain
devops, infrastructure

Research direction

Start by reviewing the Dockerfile commands that install and start ArangoDB and Azurite, then inspect how the integration tests connect to localhost ports 8529 and 10000. Confirm that both services are running and listening inside the image, and that the tests can connect to those endpoints.

Written by the indexing model from the issue text.

Description

We are following the steps outlined in this article to create a Keda build agent, and it was a successful process. We added the following steps to the docker file to include and run azurite and arangodb in the docker image to utilize in our Azure DevOps pipelines' integration tests:

RUN echo arangodb3 arangodb3/password root | debconf-set-selections
RUN echo arangodb3 arangodb3/password_again root | debconf-set-selections
RUN echo arangodb3 arangodb3/backup boolean false | debconf-set-selections
RUN echo arangodb3 arangodb3/upgrade boolean true | debconf-set-selections
RUN sudo apt-get install arangodb3=3.11.6-1
RUN sudo service arangodb3 start

RUN sudo apt-get -y install nodejs
RUN sudo apt-get install -y nodejs npm
RUN sudo npm install -g azurite
RUN sudo npm fund
RUN sudo mkdir azurite
RUN sudo azurite --silent --location azuritefiles --debug azuritefiles\debug.log &

Unfortunately the integration tests in our Azure DevOps' build pipelines are failing due to the following errors:

  • ArangoDB's connection error message: System.Net.Http.HttpRequestException : Cannot assign requested address (localhost:8529)
  • Azurite's connection error message: Connection refused (127.0.0.1:10000)

It's unclear whether or not the azurite and ArangoDB instances refrain from launching or their ports are unavailable internally within the image which sound unlikely. Regardless, we are not observing any error messages suggesting a failure in building and running the docker image.

Any suggestions on how to fix this issue?

Dominant language
JavaScript
Stars
3.1k
Forks
6.4k
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from docker/getting-started

All issues in docker/getting-started

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.