-
Notifications
You must be signed in to change notification settings - Fork 73
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
Porting a Sample Application Guide Fails on dnmonster port #2039
Comments
@amouat looks like there is a bug in this tutorial now |
ohh, the node images changed. I'll take a look. |
So the fix is to add
This will build for linux/amd64, but still seems to break for arm, so if you're on a mac, you may need to pass |
To get it to work on arm you need to add dependencies to allow it to build the
And you also need to add node-gyp to the package.json:
I'll get the tutorial updated in due course, but unfortunately it requires some re-writing so I'll need to allocate time. |
I slotted in for the next cycle @amouat |
Describe the bug
Following along with the porting a sample application guide, I was able to build the original Dockerfile, but after I made the first round of changes to the
dnmonster
nodejs microservice using the provided Dockerfile, I was unable to successfully rebuild the microservice.To Reproduce
Steps to reproduce the behavior:
Expected behavior
I would expect the build to succeed as described in the documentation. Note that the build initially fails due to claiming a need for a python runtime. I did attempt to rebuild with the python runtime added in the dockerfile, but got another failure which is what led me to file this bug.
Initial Failure
Failure w/ python added to dockerfile
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: