This image is officially deprecated in favor of the standard python image, and will receive no further updates after 2017-06-01 (Jun 01, 2017). Please adjust your usage accordingly.

See the discussion in docker-library/celery#1 and docker-library/celery#12 for more details.

  • tomee
  • php-zendserver
  • ghost
  • jetty
  • ibmjava
  • kibana
  • In most cases, using this image required re-installation of application dependencies, so for most applications it ends up being much cleaner to simply install Celery in the application container, and run it via a second command.

    See the way the sentry image handles running a Celery beat and workers for a concrete example of this pattern being employed (docker run -d --name sentry-cron ... sentry run cron and docker run -d --name sentry-worker-1 ... sentry run worker).

    Supported tags and respective Dockerfile links

    Quick reference


    Celery is an open source asynchronous task queue/job queue based on distributed message passing. It is focused on real-time operation, but supports scheduling as well.


    How to use this image

    start a celery worker (RabbitMQ Broker)

    $ docker run --link some-rabbit:rabbit --name some-celery -d celery

    check the status of the cluster

    $ docker run --link some-rabbit:rabbit --rm celery celery status

    start a celery worker (Redis Broker)

    $ docker run --link some-redis:redis -e CELERY_BROKER_URL=redis://redis --name some-celery -d celery

    check the status of the cluster

    $ docker run --link some-redis:redis -e CELERY_BROKER_URL=redis://redis --rm celery celery status

  • oraclelinux
  • couchbase
  • memcached
  • hello-seattle
  • rails
  • aerospike
  • Heads up! This alert needs your attention, but it's not super important.