Skip to content
This repository was archived by the owner on Dec 23, 2021. It is now read-only.

datproject/datbase:latest doesn't start #627

Open
SvenDowideit opened this issue Mar 6, 2018 · 2 comments · May be fixed by #628
Open

datproject/datbase:latest doesn't start #627

SvenDowideit opened this issue Mar 6, 2018 · 2 comments · May be fixed by #628

Comments

@SvenDowideit
Copy link

SvenDowideit commented Mar 6, 2018 •
edited
Loading

looking at docker hub, it looks like its an old image - the automated build setup should probably be fixed to make latest be build when master changes - or removed entirely (less good imo, but you may have reasons)

dow184@TOWER-SL:~/src/dat/datBase$ docker run --rm -it -p 8888:80 datproject/datbase npm start
npm info it worked if it ends with ok
npm info using [email protected]
npm info using [email protected]
npm info lifecycle [email protected]~prestart: [email protected]
npm info lifecycle [email protected]~start: [email protected]

> [email protected] start /usr/src/app
> npm run watch-js & npm run watch-css & npm run watch-server

npm info it worked if it ends with ok
npm info using [email protected]
npm info using [email protected]
npm info it worked if it ends with ok
npm info using [email protected]
npm info using [email protected]
npm info it worked if it ends with ok
npm info using [email protected]
npm info using [email protected]
npm info lifecycle [email protected]~prewatch-css: [email protected]
npm info lifecycle [email protected]~watch-css: [email protected]

> [email protected] watch-css /usr/src/app
> nodemon --watch client -e scss -x "npm run build-css"

npm info lifecycle [email protected]~prewatch-js: [email protected]
sh: 1: nodemon: not found
npm info lifecycle [email protected]~watch-js: [email protected]


> [email protected] watch-js /usr/src/app
> mkdir -p public/js && watchify --fast --verbose -t brfs -p [ css-extract -o bundle.css ] client/js/app.js -o public/js/app.js

npmnpm  infoinfo  lifecyclelifecycle [email protected]~watch-css: Failed to exec watch-css script
 [email protected]~prewatch-server: [email protected]
npm ERR! Linux 4.13.0-32-generic
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "watch-css"
npm ERR! node v6.9.5
npm ERR! npm  v3.10.10
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! [email protected] watch-css: `nodemon --watch client -e scss -x "npm run build-css"`
npm ERR! spawn ENOENT
npm ERR! 
npm ERR! Failed at the [email protected] watch-css script 'nodemon --watch client -e scss -x "npm run build-css"'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the datbase.org package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     nodemon --watch client -e scss -x "npm run build-css"
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs datbase.org
npm ERR! Or if that isn't available, you can get their info via:
npmnpm info lifecycle [email protected]~watch-server: [email protected]
sh: 1: watchify: not found
 ERR!     npm owner ls datbase.org
npm ERR! There is likely additional logging output above.

> [email protected] watch-server /usr/src/app
> nodemon server/cli --watch server --watch client



npm ERR! Please include the following file with any support request:
npm ERR!     /usr/src/app/npm-debug.log
sh: 1: nodemon: not found
npm info lifecycle [email protected]~watch-js: Failed to exec watch-js script
npm ERR! Linux 4.13.0-32-generic
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "watch-js"
npm ERR! node v6.9.5
npm ERR! npm  v3.10.10
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! [email protected] watch-js: `mkdir -p public/js && watchify --fast --verbose -t brfs -p [ css-extract -o bundle.css ] client/js/app.js -o public/js/app.js`
npm ERR! spawn ENOENT
npm ERR! 
npm ERR! Failed at the [email protected] watch-js script 'mkdir -p public/js && watchify --fast --verbose -t brfs -p [ css-extract -o bundle.css ] client/js/app.js -o public/js/app.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the datbase.org package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!
     mkdir -p public/js && watchify --fast --verbose -t brfs -p [ css-extract -o bundle.css ] client/js/app.js -o public/js/app.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs datbase.org
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls datbase.org
npm ERR! There is likely additional logging output above.
npm info lifecycle [email protected]~watch-server: Failed to exec watch-server script
npm ERR! Linux 4.13.0-32-generic
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "watch-server"
npm ERR! node v6.9.5
npm ERR! npm  v3.10.10
npm ERR! file sh
npm ERR!
 code ELIFECYCLE
npm ERR!npm errno  ENOENT
ERR!npm Please include the following file with any support request:
 npmERR!  ERR!syscall     /usr/src/app/npm-debug.log
 spawn
npm ERR! [email protected] watch-server: `nodemon server/cli --watch server --watch client`
npm ERR! spawn ENOENT
npm ERR! 
npm ERR! Failed at the [email protected] watch-server script 'nodemon server/cli --watch server --watch client'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the datbase.org package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     nodemon server/cli --watch server --watch client
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs datbase.org
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls datbase.org
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /usr/src/app/npm-debug.log

npm info lifecycle [email protected]~start: Failed to exec start script
npm ERR! Linux 4.13.0-32-generic
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
npm ERR! node v6.9.5
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! [email protected] start: `npm run watch-js & npm run watch-css & npm run watch-server`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] start script 'npm run watch-js & npm run watch-css & npm run watch-server'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the datbase.org package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm run watch-js & npm run watch-css & npm run watch-server
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs datbase.org
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls datbase.org
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /usr/src/app/npm-debug.log
@joehand
Copy link
Contributor

joehand commented Mar 6, 2018

It should autobuild, we were just manually doing some builds to test deployment stuff.

npm start is just used for dev. Check out the Dockerfile for the commands we run on our server. The docker just installs the production modules, so stuff like watchify isn't installed.

@SvenDowideit SvenDowideit linked a pull request Mar 6, 2018 that will close this issue
Open
@joehand
Copy link
Contributor

joehand commented Mar 6, 2018

Definitely want to get this easier to deploy! I'm not 100% knowledgeable about Docker, but hopefully I can help point the right way =).

I can start by sharing some of the things we set in production:

Environment variables:

    'TOWNSHIP_SECRET=SECRET_KEY_THING',
    'NODE_ENV=production',
    'POSTMARK_KEY=ourkey',

And the production config file.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Docker things I noticed trying to run my own dat registry SvenDowideit/datBase
2 participants
@SvenDowideit @joehand