-
Notifications
You must be signed in to change notification settings - Fork 151
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
question: (basic) best practice for using herokuish to create a runnable image #62
Comments
You'd use |
i toyed with i was able to get the desired effect with a
and running:
(in my case, my app is just a node command-line app) does that seem like a reasonable approach? |
Yeah that works alright, too. On Wed, Aug 12, 2015 at 8:58 AM, tony kerz notifications@github.com wrote:
Jeff Lindsay |
What would the |
seems to execute without any errors, but where is the new image? |
docker run --rm -v $(pwd):/tmp/app gliderlabs/herokuish /bin/herokuish buildpack build foobar works all good, where is the built image gets saved ? |
If you do not |
The built container is the one you run, you added the |
hi,
apologies in advance for beginner question (feel free to redirect me to more appropriate forum).
i have been using tutum/buildstep to build a runnable image like so as part of a home-grown build pipeline using jenkins, git and a docker runtime platform.
i recently wanted to use an iojs runtime in a node app, and it turns out that requires a more recent node buildpack than the one baked into the version of
tutum/buildstep
on dockerhub.trying to gain some background context, i did some research and came across this thread about preferring herokuish over buildstep.
along those lines, i would like to use herokuish directly without tutum or progrium buildsteps, but i'm not clear on exactly how to accomplish that.
for example would i use:
docker run gliderlabs/herokuish
at the command line, orFROM gliderlabs/herokuish
with some other commands in a Dockerfileany guidance or examples would be appreciated
best,
tony.
The text was updated successfully, but these errors were encountered: