Closed macropin closed 8 years ago
To clear the bson warning you need to have some kind of toolchain installed on your machine and node-gyp
(what OS is your container?) and then npm rebuild
will fix it.
Not sure what's causing the error RE a missing dependency. @knownasilya has there been a code regression?
Nothing that I know of..
@davemackintosh The container is built with the Docker official node:latest
image. I'd expect all the required tooling to be included.
Is that 5.x?
Yes, latest is currently also tagged 5.0
This is the Dockerfile.
Looks like an issue with npm3, and how it has changed dependencies. I think it has to do with this line: https://github.com/Strider-CD/strider/blob/master/lib/routes/admin/plugins/get_plugin_list.js#L8
Solution might be exposing the client through the strider-cli module, or installing it directly.
Give master a try.
@knownasilya thanks, my latest build seems to work fine.
All my recent docker container builds for strider have failed to start. The container gets stuck in a loop throwing the error
The workaround is to duplicate the strider-ecosystem-client code:
The container then can continue to start normally.
Any ideas where this is broken? Is this a dependency issue / bug with
strider-ecosystem-client
? Also any ideas how to clear the c++ bson warning?