Skip to content
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

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

Open
Arash-Sabet opened this issue Feb 14, 2024 · 0 comments

Comments

@Arash-Sabet
Copy link

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant