exited with code 0 about meteor-launchpad HOT 3 CLOSED

Looks like you are overwriting the command that starts the app by using:
command: chmod a+rwx -R /var/lib/application

https://docs.docker.com/engine/reference/run/#cmd-default-command-or-options

from meteor-launchpad.

To be clear, that means your container is starting up and running chmod a+rwx -R /var/lib/application instead of starting the app with node main.js like it should be. So this isn't a problem with the image. It's your usage of it. It's because you're overriding the command that starts the app to do a permissions change and then the app never gets started. If you want to do some custom steps on the filesystem inside the container, you should either add some steps to your Dockerfile or maybe even fork the project and create your own custom image.

from meteor-launchpad.

Thanks, it worked;) I put that line in my docker-compose because I had no writing permissions somehow, but that seems to be gone for what reason ever

from meteor-launchpad.