Sentry background jobs instruction about docs HOT 8 CLOSED

Your backgrounded task (sentry celery worker -B &) is just another celery worker and celery beat; and could break since there is not an init process in the container to monitor secondary process (ie not really the "docker way"). I am not sure if your plain celery containers are even working since that backgrounded task was a new celery worker and would thus make the warning go away.

It seems that there must be more happening with the celery embedded with sentry vs running plain celery with a redis url. Have you tried running the embedded celery in separate containers?

docker run -d --name log-analyser-celery-beat --link some-redis:redis sentry sentry celery beat
docker run -d --name log-analyser-celery-worker1 --link some-redis:redis sentry sentry celery worker

from docs.

The worker seems to also need postgres. I got it working using the following.

docker run -d --name celery-beat --link redis:redis --link postgres:postgres -e CELERY_BROKER_URL=redis://redis sentry sentry celery beat
docker run -d --name celery-worker1 --link redis:redis --link postgres:postgres -e CELERY_BROKER_URL=redis://redis sentry sentry celery worker

from docs.

@aheuermann, is there not a way to run plain celery workers (ie the celery image) or do they have to be celery that is included with sentry? What extra configuration is being done to them by sentry?

Also, you shouldn't need CELERY_BROKER_URL when using the embedded celery since it is setup in docker-links.conf.py.

from docs.

@yosifkit & @aheuermann both suggestions didn't work.

from docs.

@yosifkit I don't know much about celery (or the internals of sentry for that matter). I'm guessing it needs the sentry code packaged with it though as that is where the tasks are defined. Also, I found some celery config here.

from docs.

/cc @mattrobenolt, the new maintainer of the sentry image! 😄

from docs.

I'm going to be making this easier soon. :) So hang in there while we take over.

from docs.

If this is still an issue, reopen under https://github.com/getsentry/docker-sentry/issues

/cc @yosifkit can you close this? :)

from docs.