Currently there's no way to pass in one off environment variables you may need or want to override from the existing application.

This flow allows someone to build a docker image, but getting it running with the container registry takes some work and requires using the docker CLI directly. This new command will need to handle the following:

• heroku docker registry login
• docker tag registry.heroku.com//web
• docker push

Currently, local:run only does web but many apps use multiple process types. This will allow a more foreman style of app boot.

The push command should detect and support process types in the heroku.yml. For example:

run:
  web: start.sh
  worker: worker.sh

This dependent on:

• Supporting heroku.yml process types in /packs/launcher
• determining the order of precedence for Procfile and heroku.yml.

Convert the bin/test script to tests in the test dir.

Running $ heroku local:build --config in windows runs into this problem when trying to build the env dir layer:

COPY failed: stat /var/lib/docker/tmp/docker-builder806846994/env: no such file or directory

I believe this is because tar pathing behaves potentially different on windows, so docker can't find the env dir.

Like the node.js test, create one for:

• Ruby
• Java
• Python
• PHP
• Go

For buildpack development, it'd be great if this supported building against a local checked out buildpack repo.

Users shouldn't need to manually remove the cache file, but sometimes there is need to perform a build with a clean cache.

The /packs/launcher just hangs when trying to boot an app with the heroku metrics buildpack. Once you remove the .profile.d script it works.