Dokku v0.3.10 - ! [remote rejected] master -> master (pre-receive hook declined) #841

Closed
andykenward opened this Issue Dec 23, 2014 · 21 comments

Projects

None yet

7 participants

@andykenward

Fresh install of Dokku and I still cant get an app to deploy when pushing. Here is the log output

https://gist.github.com/andykenward/8f815099c679bcfbad14

@michaelshobbs
Member

Seems to be failing in the nodejs buildpack. I've seen this when the downloading of node fails (silently unfortunately).... Verify network connectivity from the container perhaps?

@lgierth
lgierth commented Jan 12, 2015

I'm seeing what seems to be the same issue on e0c49ec, with dokku-buildpack-jekyll-nginx and this repo: https://github.com/lgierth/lars.meshnet.berlin

https://gist.github.com/andykenward/8f815099c679bcfbad14#comment-1370409

@lgierth
lgierth commented Jan 12, 2015

Verify network connectivity from the container perhaps?

I can't get DNS to work from within a container, so far. ICMP pings work.

@lgierth
lgierth commented Jan 12, 2015

Okay, got it, for me it was a matter of uncommenting DOCKER_OPTS="--dns 8.8.8.8 --dns 8.8.4.4 in /etc/default/docker.

@josegonzalez
Member

I wonder if we can use our docker-args pluginhook to set this in our vms without modifying the default docker file. @michaelshobbs thoughts?

@michaelshobbs
Member

It's definitely feasible. However I don't think we should dictate DNS servers.

@josegonzalez
Member

Why not? The alternative is having a shitty experience for our users. If anything, we can default to those options and let users override them where desired?

@michaelshobbs
Member

Yeah it's probably fine as long as we clearly document it and provide a simple way to override them.

@rchrd2
rchrd2 commented Jan 12, 2015

I am having this same issue, but uncommenting DOCKER_OPTS="--dns 8.8.8.8 --dns 8.8.4.4 in /etc/default/docker did not solve it. Could anybody please shed some light on this? What specifically is failing? Everything was running smoothly for me last week and now it just stopped working? Does dokku depend on external libraries that could change, such as buildpacks?

I am running dokku v0.3.12. Trying to deploy nodejs, which appears to have been updated a very recently https://github.com/heroku/heroku-buildpack-nodejs/releases. Does dokku pull the latest buildpacks by default?

@rchrd2
rchrd2 commented Jan 13, 2015

Here's an update to my debugging. I was able to confirm that the issue has to do with the content of my repository. Thus, this seems like a bug. Why would the files in a repo break dokku? In this case, the files are just a basic website (javascript, css, html, images).

Below is a list of the filenames without the contents. Note some of the files have strange names because this page was automatically downloaded with a web browser to create a static version of a squarespace site:

 public/VF/index.html
 public/VF/vf_files/commerce-2b2463360721c566c0744b54e3a6cccd-min.js
 public/VF/vf_files/commerce-7cd1be72900e2a5a526a8dcbea220a1a-min.css
 public/VF/vf_files/common-1b991f22508de19503322551c272d732-min.js
 public/VF/vf_files/js
 public/VF/vf_files/oKmauz-dLaAke3cUDynMnMGs2QiQJeBQVb_8QEyGvrJfenCffFHN4UJLFRbh52jhWD9DwcjUjhItZQsKw24K5ewDFQIU5QwowsTyiaiaO1ZyjhB0ieZyScunjkoRdhXCicBRjAoXZcBkdAlROcFzdPUhjAFyd1scjW4l-hw0SaBujW48Sagyjh90jhNlOfG0icBRjAoXZcBkdAlRO1FUiABkZWF3jAF8OcFzdPJwSY4zpe8ljPu0daZyJ68c.js
 public/VF/vf_files/saved_resource
 public/VF/vf_files/saved_resource(1)
 public/VF/vf_files/site.css
 public/VF/vf_files/{common,util,stats}.js
 public/VF/vf_files/{main,places}.js
@michaelshobbs
Member

A deployment log with tracing on would probably help

@rchrd2
rchrd2 commented Jan 13, 2015

I broke down the steps to confirm that it is this one file (with a crazy long name) that is breaking it.

Steps to reproduce the bug in gist: https://gist.github.com/rchrd2/76d439ad07bd87d556f2.

Dokku trace output: https://gist.github.com/rchrd2/76d439ad07bd87d556f2#file-trace-output-txt

@michaelshobbs
Member

Interesting. Must be in the git-receive hook. Can you please open a new issue as I believe the root causes to be quite different? Thanks!

@simenbrekken
Contributor

I've run into a similar problem just now, it solved itself by rebooting the VPS (Rackspace). Very strange.

Failed push: https://gist.github.com/7a12be929ad06373c556
Successful push (after reboot): https://gist.github.com/simenbrekken/7a12be929ad06373c556#file-02-trace-log

@michaelshobbs
Member

Seems almost certainly a (transient) networking issue of some sort.

@josegonzalez
Member

I'm guessing heroku uses an http proxy for s3 requests like this. I wonder if we could do similar and have a command that downloads requirements to the box during installation? shrug

@michaelshobbs
Member

@josegonzalez that seems like significant complexity though. do you think that should even be a concern of dokku?

@josegonzalez
Member

No, I guess not. Do you mind updating docs with potential fixes for this issue and closing this one out?

@michaelshobbs
Member

Updating docs with what now?

@josegonzalez
Member

Stuff like:

  • Check your docker dns
  • Try running the command inside the container
  • Try deploying again - it may be a transient issue with upstream

shrug

@rdetert
rdetert commented Jul 30, 2015

Yeah this was the issue for me as well. I accidentally had the .git folder from a third party cloned repo inside a subfolder of my main repo. facepalm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment