jackdh / RasaTalk

A chatbot framework for Rasa NLU
MIT License
297 stars 87 forks source link

Docker compose up to get error #12

Closed gowtham4gs closed 5 years ago

gowtham4gs commented 5 years ago

$ RUN docker compose up -d E: Unable to locate package libpng12-0 ERROR: Service 'rasatalk' failed to build: The command '/bin/sh -c apt-get update && apt-get install libpng12-0 bzip2' returned a non-zero code: 100

Im learner please give detailed configuration details thanks!

jackdh commented 5 years ago

Hi @gowtham4gs

I think the docker-compose might be slightly broken currently as other have reported this issue.

It's high on my list to fix however! For now it might be best to manually install it if that is an open.

You can do that by

1 - Clone the repository 2 - yarn install (If this fails run as admin / sudo) 3 - You'll then need to create the .env file (you can copy it from the example.env file) 4 - Update the .env file to point at a mongodb database / rasa NLU service. These can be spun up locally with docker independently if you do not have them. 5 - yarn start

That should get you up and running.

gowtham4gs commented 5 years ago

Hi jackdh,

thanks for replied, im followed all your steps but i got error in cross env when trigger $yarn start

Below error showing in my ubuntu terminal: root@CD29UBUNTU:/home/administrator/Downloads/test/RasaTalk# yarn start yarn run v1.13.0 $ cross-env NODE_ENV=development node server /bin/sh: 1: cross-env: not found error Command failed with exit code 127. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. root@CD29UBUNTU:/home/administrator/Downloads/test/RasaTalk#

jackdh commented 5 years ago

Can you please try removing the node_modules folder then running yarn install again?

Thanks

gowtham4gs commented 5 years ago

cleaned now getting this type exceptions:

$yarn start yarn run v1.13.0 $ cross-env NODE_ENV=development node server the server/replset/mongos/db options are deprecated, all their options are supported at the top level of the options object [poolSize,ssl,sslValidate,sslCA,sslCert,sslKey,sslPass,sslCRL,autoReconnect,noDelay,keepAlive,keepAliveInitialDelay,connectTimeoutMS,family,socketTimeoutMS,reconnectTries,reconnectInterval,ha,haInterval,replicaSet,secondaryAcceptableLatencyMS,acceptableLatencyMS,connectWithNoPrimary,authSource,w,wtimeout,j,forceServerObjectId,serializeFunctions,ignoreUndefined,raw,bufferMaxEntries,readPreference,pkFactory,promiseLibrary,readConcern,maxStalenessSeconds,loggerLevel,logger,promoteValues,promoteBuffers,promoteLongs,domainsEnabled,checkServerIdentity,validateOptions,appname,auth,user,password,authMechanism,compression,fsync,readPreferenceTags,numberOfRetries,auto_reconnect,minSize,monitorCommands,retryWrites,useNewUrlParser] the server/replset/mongos/db options are deprecated, all their options are supported at the top level of the options object [poolSize,ssl,sslValidate,sslCA,sslCert,sslKey,sslPass,sslCRL,autoReconnect,noDelay,keepAlive,keepAliveInitialDelay,connectTimeoutMS,family,socketTimeoutMS,reconnectTries,reconnectInterval,ha,haInterval,replicaSet,secondaryAcceptableLatencyMS,acceptableLatencyMS,connectWithNoPrimary,authSource,w,wtimeout,j,forceServerObjectId,serializeFunctions,ignoreUndefined,raw,bufferMaxEntries,readPreference,pkFactory,promiseLibrary,readConcern,maxStalenessSeconds,loggerLevel,logger,promoteValues,promoteBuffers,promoteLongs,domainsEnabled,checkServerIdentity,validateOptions,appname,auth,user,password,authMechanism,compression,fsync,readPreferenceTags,numberOfRetries,auto_reconnect,minSize,monitorCommands,retryWrites,useNewUrlParser] Mongo connection: 0 Initializing Botkit v0.6.21 info: ** No persistent storage method specified! Data may be lost when process shuts down. debug: Setting up a handler for webserver_up debug: Setting up a handler for message_received The DLL manifest is missing. Please run npm run build:dll Done in 1.62s.

jackdh commented 5 years ago

Okay that looks fine,

Please now run

yarn build:dll

or

npm run build:dll

This is something that react boilerplate requires us to do sometimes! I'm honestly not sure why but I get it some times!

gowtham4gs commented 5 years ago

Hi :-),

I got exception in UI :+1:

ERROR in ./app/images/logo.png Module build failed (from ./node_modules/image-webpack-loader/index.js): Error at Process.ChildProcess._handle.onexit (internal/child_process.js:232:19) at onErrorNT (internal/child_process.js:407:16) at process._tickCallback (internal/process/next_tick.js:63:19) @ ./app/containers/LoginPage/index.js 21:0-35 102:44-48 @ ./app/containers/App/index.js @ ./app/app.js @ multi eventsource-polyfill webpack-hot-middleware/client?reload=true ./app/app.js ERROR in ./app/images/link.png Module build failed (from ./node_modules/image-webpack-loader/index.js): Error at Process.ChildProcess._handle.onexit (internal/child_process.js:232:19) at onErrorNT (internal/child_process.js:407:16) at process._tickCallback (internal/process/next_tick.js:63:19) @ ./app/containers/Synonyms/index.js 31:0-41 117:20-24 @ ./app/containers/Synonyms/Loadable.js @ ./app/containers/HomePage/index.js @ ./app/containers/HomePage/Loadable.js @ ./app/containers/App/index.js @ ./app/app.js @ multi eventsource-polyfill webpack-hot-middleware/client?reload=true ./app/app.js ERROR in ./app/components/Cards/placeholder-male.png Module build failed (from ./node_modules/image-webpack-loader/index.js): Error at Process.ChildProcess._handle.onexit (internal/child_process.js:232:19) at onErrorNT (internal/child_process.js:407:16) at process._tickCallback (internal/process/next_tick.js:63:19) @ ./app/components/Cards/ProfileCard.js 7:0-51 108:60-73 @ ./app/containers/TalkWrapper/index.js @ ./app/containers/TalkWrapper/Loadable.js @ ./app/containers/HomePage/index.js @ ./app/containers/HomePage/Loadable.js @ ./app/containers/App/index.js @ ./app/app.js @ multi eventsource-polyfill webpack-hot-middleware/client?reload=true ./app/app.js ERROR in ./app/images/iIcon.png Module build failed (from ./node_modules/image-webpack-loader/index.js): Error at Process.ChildProcess._handle.onexit (internal/child_process.js:232:19) at onErrorNT (internal/child_process.js:407:16) at process._tickCallback (internal/process/next_tick.js:63:19) @ ./app/containers/Agents/index.js 22:0-37 153:26-31 @ ./app/containers/Agents/Loadable.js @ ./app/containers/HomePage/index.js @ ./app/containers/HomePage/Loadable.js @ ./app/containers/App/index.js @ ./app/app.js @ multi eventsource-polyfill webpack-hot-middleware/client?reload=true ./app/app.js ERROR in ./app/images/agent.png Module build failed (from ./node_modules/image-webpack-loader/index.js): Error at Process.ChildProcess._handle.onexit (internal/child_process.js:232:19) at onErrorNT (internal/child_process.js:407:16) at process._tickCallback (internal/process/next_tick.js:63:19) @ ./app/containers/Agents/index.js 25:0-45 113:61-74 @ ./app/containers/Agents/Loadable.js @ ./app/containers/HomePage/index.js @ ./app/containers/HomePage/Loadable.js @ ./app/containers/App/index.js @ ./app/app.js @ multi eventsource-polyfill webpack-hot-middleware/client?reload=true ./app/app.js

please give suggest. thanks

gowtham4gs commented 5 years ago

triggered $yarn build:dll and $npm run build:dll same error showing

gowtham4gs commented 5 years ago

in terminal error: https://gist.github.com/jackdh/a6bf9f8acf930adc6d17867ec43e2de6

gowtham4gs commented 5 years ago

in Browser error :+1: screenshot from 2019-01-28 19-47-07

jackdh commented 5 years ago

Interesting, it looks like webpack is not bundling the images with it,

Can you try just with localhost:5001 ? I don't think that would be the issue but it could be.

Also what are you using to run the application?

gowtham4gs commented 5 years ago

:-) $yarn start using to running...you have any other steps please guide me.

gowtham4gs commented 5 years ago
  1. npm run build:dll
  2. Yarn start

above steps im using for run.

gowtham4gs commented 5 years ago

Successfully run. but exception receiving duckling server,please suggest

Thanks

gowtham4gs commented 5 years ago

finished all configuration but getting error like below. (node:7908) Warning: a promise was created in a handler at /home/administrator/Downloads/test/RasaTalk/server/mongo/controllers/permissions/permissions.js:66:10 but was not returned from it, see http://goo.gl/rRqMUw

and your dashborad showing rasa stats 3 projects running but mine showing 2 only.

jackdh commented 5 years ago

That will be because on my dashboard I have a few real running projects which I've hidden from the demo account. So it'll say 3 but only allow you to see 2.

That is just a warning which I need to clean up it shouldn't affect you however!

gowtham4gs commented 5 years ago

All issues resolved,

Thanks Jackdh

jackdh commented 5 years ago

No worries @gowtham4gs sorry this was such a terrible setup procedure! I wish I had some more time to try and makes things smoother!

Btibert3 commented 5 years ago

Is the plan still to stay away from using docker-compose to build? I spun up a droplet on Digital Ocean to play around, and got the same error (Unable to locate package libpng12-0).

jackdh commented 5 years ago

Hey @Btibert3 Yeah it's been really annoying me lately, I've attempted to get docker working again however keep running into little issues with unknown causes.

You an bypass the libpng error by not using the slim version of node and then removing the install command for libpng however that then gets blocked a little later on by the chunk asset optimization.

The current way to get it to work which isn't ideal is to first build the application locally then bypass the build step in docker. This is actually faster overall I've found however does then require installing node on the host machine which again is not ideal.

I'm looking into it abit over this weekend however am a bit stripped for time.