meteor-launchpad | A base Docker image for Meteor applications | Continuous Deployment library
kandi X-RAY | meteor-launchpad Summary
kandi X-RAY | meteor-launchpad Summary
A base Docker image for Meteor applications.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of meteor-launchpad
meteor-launchpad Key Features
meteor-launchpad Examples and Code Snippets
Community Discussions
Trending Discussions on meteor-launchpad
QUESTION
I'm running a docker container on heroku, but I can't seem to understand how it works.
Locally I'm able to run a command docker run imageName ls -al
, but on heroku: heroku run "ls -al"
it returns ./entrypoint.sh: line 34: exec: ls -al: not found
. Although when I run heroku run ls
without arguments, it works as expected. (as another experiment I've run heroku run bash
and then ./entrypoint.sh ls -al
that also works).
What's happening here?
Comments updates:Damien MATHIEU: the image I try to run is this https://github.com/jshimko/meteor-launchpad - and my docker file is:
...
ANSWER
Answered 2017-Oct-28 at 05:31Edit-2 - 28-Oct-2017
Latest update from Heroku
We've triaged this, and we're definitely not implementing Docker-compatible behaviour here. Thanks for catching this - we'll get it fixed.
Original answer
Your error is quite clear from below itself
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install meteor-launchpad
Meteor Launchpad supports setting custom build options in one of two ways. You can either create a launchpad.conf config file in the root of your app or you can use Docker build args. The currently supported options are to install PhantomJS, GraphicsMagick, MongoDB, or any list of apt-get dependencies (Meteor Launchpad is built on debian:jesse). If you choose to install Mongo, you can use it by not supplying a MONGO_URL when you run your app container. The startup script will then start Mongo inside the container and tell your app to use it. If you do supply a MONGO_URL, Mongo will not be started inside the container and the external database will be used instead. Note that having Mongo in the same container as your app is just for convenience while testing/developing. In production, you should use a separate Mongo deployment or at least a separate Mongo container.
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page