How change address about npm_lazy HOT 2 CLOSED

I you ran docker exec and can see that the config.js module your loading has indeed changed in the container, but the server still uses the default configuration, then it might be some unexpected behavior related to how docker manages CMD/ENTRYPOINT/COPY/ADD/VOLUME and the passed container options.

It is just an assumption, but it might well be that the container started the server before your changes have been written and committed to the container's filesystem. I'll allocate some time in the morning and see if I can reproduce just what your experiencing and update the README accordingly.

from npm_lazy.

Hi @brunobatista! I revamped the container, with support for configuring npm_lazy with run commands. I'll close the issue, but please give it a go and re-open it if you still have any difficulties with running a custom server.

from npm_lazy.