Open realies opened 5 years ago
Hi,
Thank you for reporting this.
~I know npm
has had some issues this past week but I don't know if this could be related to that.~ Definitely not related to the npm
issues this week. It looks like it has to do with sqs-insight
loading much quicker than elasticmq. This was probably introduced by the use of dynamic endpoints.
I'll investigate 🕵️ 👀
Supervisord doesn't support process dependencies with the autostart feature;
See supervisor bug #122.
Workaround: https://github.com/bendikro/supervisord-dependent-startup
Example: https://github.com/bendikro/supervisord-dependent-startup/blob/master/example.md
I'll work on implementing this shortly.
@roribio This is perhaps a stupid question, but I haven't worked with python much. How do I implement that workaround? I've spent some time with the supervisord-dependent-startup
package and I'm trying to build a new image of alpine-sqs
with that package included. I've tried copying that full directory under /etc/supervisor
and adding the following to supervisord.conf
:
[eventlistener:dependentstartup]
command=python /etc/supervisor/supervisord_dependent_startup/supervisord_dependent_startup.py -c /etc/supervisor/supervisord.conf
autostart=true
events=PROCESS_STATE
However that doesn't seem to work. When I run this as a local_sqs
container via docker-compose
I get:
local_sqs_1 | 2019-02-21 06:22:46,611 INFO spawned: 'dependentstartup' with pid 13
local_sqs_1 | 2019-02-21 06:22:46,658 INFO exited: dependentstartup (exit status 1; not expected)
I'll be happy to submit a PR to fix this issue once I can figure out how to include this package. Do you have any advice?
Hey @JackWCollins,
Thanks for picking this up! I don't think it's a stupid question at all, I'm not a Python expert either.
I did some research and found a project that's using this same plugin, here. It's structured similarly as this project. Upon inspection, I conclude/assume the following:
pip
. See example here.For non-editable installs, the project is built locally in a temp dir and then installed normally. Note that if a satisfactory version of the package is already installed, the VCS source will not overwrite it without an –upgrade flag. VCS requirements pin the package version (specified in the setup.py file) of the target commit, not necessarily the commit itself.
-- Reference: PIP User Manual - VCS Support.
pip
is included with the alpine-base
distribution and no further installation is required. I would double-check this is the case though.pip
installs binaries to /usr/local/bin
on Alpine Linux. See example here.I hope this helps! If you can get it to work, I'm glad to merge your changes and update the image on Docker Hub.
Thanks again, Ronald
Upon booting the container up via docker-composer there is errors until something fully initializes: