InfraBox icon indicating copy to clipboard operation
InfraBox copied to clipboard

Dev Setup

Open jppianta opened this issue 6 years ago • 4 comments

Describe the bug I am new to the repo and I am trying to setup my machine for development. I managed to add all the dependencies although I have some doubts about the python 2.7 requirement and why there is no Pipfile in the repo.

I am trying to start the api service with command ./ib.py services start api, but I am getting a maximum recursion depth exceeded under super(SSLContext, SSLContext).options.__set__(self, value). The storage and dashboard-client services start normally.

Desktop (please complete the following information):

  • OS: Mac OS Catalina 10.15.2

jppianta avatar Jan 22 '20 20:01 jppianta

The dev documentation in this repo needs to be updated. On linux machines we're using k3s to create a local single node cluster and deploy infrabox using run_k3s.sh. Sadly there's no k3s for Mac OS, but the kubernetes feature of Docker Desktop is a good substitute. I did the necessary modifications to run_k3s at the osx-dev branch and created a gist with some instructions here.

meranos avatar Jan 23 '20 15:01 meranos

Thank you for the help. I managed to deploy it with Docker Desktop. I am only having an issue with the dashboard-client that I don't know how to solve. When I print the logs from the static pod I get the following error after the > Listening at http://localhost:8080 message:

(node:79) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: Exited with code 3 (node:79) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

jppianta avatar Jan 29 '20 05:01 jppianta

These warnings should at least not cause major issues. What's going wrong with the dashboard?

meranos avatar Jan 29 '20 12:01 meranos

I have nothing on my localhost:8080. I don't think it is just a warning, it says it exited with code 3. When I run the ui outside the cluster I get no errors.

jppianta avatar Jan 29 '20 14:01 jppianta