Leander Roters

@fruitl00p I ran into similar problems you are describing. I don't think the new-relic daemon segfaults. I can actually start it manually, when attached to the container with: `$ /app/.heroku/php/bin/newrelic-daemon...

seem the logfile gets touched during the build-process as root here? https://github.com/heroku/heroku-buildpack-php/blob/f2b37ffa3aac00ccc6cb11405325298f40904028/bin/util/newrelic.sh#L29

It seems on heroku processes run as root (fpm, as well as the new-relic daemon). According to their docs (https://devcenter.heroku.com/articles/runtime-principles) > Superficially, it is convenient to think of each of...

have tried `chmod 777` on the logfile, new relic daemon is phoning home just fine with the modified buildpack forked from `heroku/heroku-buildpack-php` https://github.com/wesrc/heroku-buildpack-php-1/commit/b28a37ea76bf09a8ac84dd2a28e8cf10c2672f19. /cc @dzuelke

@fesor see #112

@zombor which docker version are you running? I have similar issues and wonder wether upgrading from docker 1.0 to 1.3 is related. possibly related to #8 as well? When running...

@lordelph I ran into the same test failing for my PR #112. I can reproduce the failing test locally. Outputbuffer magic :neckbeard: Hints on how to solve this are appreciated

@lordelph @Pawka I managed to solve the failing builds by installing phpunit 4.2.2 with composer. see #112