Open wandonye opened 6 years ago
After fixed several problems in Dockerfile, I came across this
Dockerfile
meanjs | > gulp meanjs | meanjs | gulp[31]: ../src/node_contextify.cc:628:static void node::contextify::ContextifyScript::New(const v8::FunctionCallbackInfo<v8::Value>&): Assertion `args[1]->IsString()' failed. meanjs | 1: 0x8d1bc0 node::Abort() [gulp] meanjs | 2: 0x8d1c95 [gulp] meanjs | 3: 0x906b27 node::contextify::ContextifyScript::New(v8::FunctionCallbackInfo<v8::Value> const&) [gulp] meanjs | 4: 0xb87f9b [gulp] meanjs | 5: 0xb89f32 v8::internal::Builtin_HandleApiCall(int, v8::internal::Object**, v8::internal::Isolate*) [gulp] meanjs | 6: 0xa1be885c01d meanjs | Aborted meanjs | npm ERR! code ELIFECYCLE meanjs | npm ERR! errno 134 meanjs | npm ERR! meanjs@0.6.0 start: `gulp` meanjs | npm ERR! Exit status 134 meanjs | npm ERR! meanjs | npm ERR! Failed at the meanjs@0.6.0 start script. meanjs | npm ERR! This is probably not a problem with npm. There is likely additional logging output above. meanjs | meanjs | npm ERR! A complete log of this run can be found in: meanjs | npm ERR! /root/.npm/_logs/2018-09-17T04_48_28_916Z-debug.log ^CERROR: Aborting.
This boilerplate is so buggy with Docker. How are you guys going to deploy your projects?
After fixed several problems in
Dockerfile
, I came across thisThis boilerplate is so buggy with Docker. How are you guys going to deploy your projects?