Skip to content
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

error running decking on Centos 6 #35

Closed
benmathews opened this issue Jun 26, 2014 · 3 comments · Fixed by #38
Closed

error running decking on Centos 6 #35

benmathews opened this issue Jun 26, 2014 · 3 comments · Fixed by #38

Comments

@benmathews
Copy link

I'm getting the below error running decking. I've got nodejs-0.10.28-1.el6.x86_64 installed.

[ben@localhost decking-example-master]$ decking build all
Looking up build data for decking/example-api
Building image decking/example-api from ./docker/api/Dockerfile
Uploading compressed context...
Error: HTTP code is 500 which indicates error: server error - null
at Modem.buildPayload (/usr/lib/node_modules/decking/node_modules/dockerode/node_modules/docker-modem/lib/modem.js:134:15)
at ClientRequest. (/usr/lib/node_modules/decking/node_modules/dockerode/node_modules/docker-modem/lib/modem.js:95:12)
at ClientRequest.EventEmitter.emit (events.js:117:20)
at HTTPParser.parserOnIncomingClient as onIncoming
at HTTPParser.parserOnHeadersComplete as onHeadersComplete
at Socket.socketOnData as ondata
at Pipe.onread (net.js:527:27)
Error: read ECONNRESET
at errnoException (net.js:904:11)
at Pipe.onread (net.js:558:19)
[WARN] Could not remove Dockerfile

@danielwegener
Copy link

Confirmed on Linuxmint 16:
Error: HTTP code is 500 which indicates error: server error - null
/var/log/upstart/docker.log
says

2014/07/16 00:19:20 POST /build?t=tracee%2Fgreylog-elasticsearch
[382e0568] +job build()
Dockerfile cannot be empty
[382e0568] -job build() = ERR (1)
[error] server.go:1048 Error making handler: Dockerfile cannot be empty
[error] server.go:90 HTTP Error: statusCode=500 Dockerfile cannot be empty

@stephenmelrose
Copy link
Contributor

@amalagaura The update hasn't been rolled out to npm yet. Sorry. Going to merge some stuff this weekend and will pump out a new version.

For now, you can try installing from a local checkout of master if you want? Clone the repo then do an npm install -g pointing at the local path to your checkout. This will have the latest change and should hopefuly fix your issue until we get a proper version out.

@amalagaura
Copy link

@stephenmelrose Thanks, I realized that after I posted and started looking at the releases so I deleted the comment ;-)

I did a crash course in npm and do the have head running locally now on the box. Thanks for your attention.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants