dokku: ! [remote rejected] master -> master (pre-receive hook declined) when trying to push a Pelican static blog

Output of trace “on”: https://gist.github.com/dm-wyncode/c67e55786fe21060d5a2944614731291

Description of problem:

I have installed Dokku on a Linode instance.

To test that Dokku functions as expected, I deployed a sample Rails app from https://github.com/heroku/ruby-rails-sample

The Rails app deploys with no problems: http://ruby-rails-sample.zip.thruhere.net/

I then decided to try deploying a Pelican static site as described in this blog: https://launchbylunch.com/posts/2014/Jan/23/blog-tech-stack/

I used this repo to create my own Pelican site: https://github.com/sehrope/pelican-dokku-bare

Output of the following commands

• uname -a: Linux zip.thruhere.net 4.5.5-x86_64-linode69 #3 SMP Fri May 20 15:25:13 EDT 2016 x86_64 x86_64 x86_64 GNU/Linux
• free -m: total used free shared buffers cached Mem: 1999 1608 391 23 32 1276 -/+ buffers/cache: 298 1700 Swap: 511 0 511
• docker version: Docker version 1.11.2, build b9f10c9
• docker -D info:

Containers: 8 Running: 2 Paused: 0 Stopped: 6 Images: 12 Server Version: 1.11.2 Storage Driver: devicemapper Pool Name: docker-8:0-130165-pool Pool Blocksize: 65.54 kB Base Device Size: 10.74 GB Backing Filesystem: ext4 Data file: /dev/loop0 Metadata file: /dev/loop1 Data Space Used: 2.847 GB Data Space Total: 107.4 GB Data Space Available: 20.87 GB Metadata Space Used: 3.633 MB Metadata Space Total: 2.147 GB Metadata Space Available: 2.144 GB Udev Sync Supported: true Deferred Removal Enabled: false Deferred Deletion Enabled: false Deferred Deleted Device Count: 0 Data loop file: /var/lib/docker/devicemapper/devicemapper/data WARNING: Usage of loopback devices is strongly discouraged for production use. Either use --storage-opt dm.thinpooldev or use --storage-opt dm.no_warn_on_loop_devices=true to suppress this warning. Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata Library Version: 1.02.77 (2012-10-15) Logging Driver: json-file Cgroup Driver: cgroupfs Plugins: Volume: local Network: null host bridge Kernel Version: 4.5.5-x86_64-linode69 Operating System: Ubuntu 14.04.4 LTS OSType: linux Architecture: x86_64 CPUs: 1 Total Memory: 1.953 GiB Name: zip.thruhere.net ID: UQJJ:UUB2:RKJ5:YDKY:UC55:CG2E:K25I:KVQJ:ZL4Y:QXYE:JE7Q:QX6K Docker Root Dir: /var/lib/docker Debug mode (client): true Debug mode (server): false Registry: https://index.docker.io/v1/ WARNING: No swap limit support

• sigil -v: 0.4.0
• docker run -ti gliderlabs/herokuish:latest herokuish version:

herokuish: 0.3.13 buildpacks: emberjs.tgz latest buildpack-nginx v5 heroku-buildpack-clojure v75 heroku-buildpack-erlang fa17af9 heroku-buildpack-go v36 heroku-buildpack-gradle v17 heroku-buildpack-grails v20 heroku-buildpack-java v44 heroku-buildpack-multi v1.0.0 heroku-buildpack-nodejs v90 heroku-buildpack-php v102 heroku-buildpack-play v26 heroku-buildpack-python v80 heroku-buildpack-ruby v146 heroku-buildpack-scala v70

• dokku version: 0.5.7
• dokku plugin: plugn: dev 00_dokku-standard 0.5.7 enabled dokku core standard plugin 20_events 0.5.7 enabled dokku core events logging plugin apps 0.5.7 enabled dokku core apps plugin build-env 0.5.7 enabled dokku core build-env plugin certs 0.5.7 enabled dokku core certificate management plugin checks 0.5.7 enabled dokku core checks plugin common 0.5.7 enabled dokku core common plugin config 0.5.7 enabled dokku core config plugin docker-options 0.5.7 enabled dokku core docker-options plugin domains 0.5.7 enabled dokku core domains plugin enter 0.5.7 enabled dokku core enter plugin git 0.5.7 enabled dokku core git plugin logs 0.5.7 enabled dokku core logs plugin named-containers 0.5.7 enabled dokku core named containers plugin nginx-vhosts 0.5.7 enabled dokku core nginx-vhosts plugin plugin 0.5.7 enabled dokku core plugin plugin postgres 1.0.0 enabled dokku postgres service plugin proxy 0.5.7 enabled dokku core proxy plugin ps 0.5.7 enabled dokku core ps plugin shell 0.5.7 enabled dokku core shell plugin storage 0.5.7 enabled dokku core storage plugin tags 0.5.7 enabled dokku core tags plugin tar 0.5.7 enabled dokku core tar plugin
• docker inspect CONTAINER_ID (if applicable): (BEWARE: docker inspect will print environment variables for some commands, be sure you’re not exposing any sensitive information when posting issues. You may replace these values with XXXXXXX):
• cat /home/dokku/<app>/nginx.conf (if applicable):
• Link to the exact repository being deployed (if possible/applicable): https://github.com/sehrope/pelican-dokku-bare
• If a deploy is failing or behaving unexpectedly:
  • Application name: blog
  • The type of application being deployed (node, php, python, ruby, etc.): python Pelican static blog
  • If using buildpacks, which custom buildpacks are in use
  • If using a Dockerfile, the contents of that file
  • If it exists, the contents of your Procfile.
• Output of failing dokku commands after running dokku trace on (BEWARE: trace on will print environment variables for some commands, be sure you’re not exposing any sensitive information when posting issues. You may replace these values with XXXXXXX):

Environment details (AWS, VirtualBox, physical, etc.): Linode instance

How was dokku installed?: using https://github.com/dokku/dokku/blob/master/bootstrap.sh

How reproducible: so far only with a Pelican static blog. A Ruby Rails app deploys as expected.

Steps to Reproduce:

1. git push dokku master where remote is set appropriately

Actual Results: master (pre-receive hook declined)

Expected Results:

app deployed as described in this blog post: https://launchbylunch.com/posts/2014/Jan/23/blog-tech-stack/

Additional info: I’m new to Dokku. It’s probably something I am not understanding that is different about the Pelican static blog. I tried various things in an app.json file with no success. I tried setting

dokku config:set blog BUILDPACK_URL=https://github.com/getpelican/heroku-buildpack-pelican

without any success.