allworldit/celery repository overview

⁠Container Information

Container Source⁠ - GitHub Mirror⁠

This is the Conarx Containers Celery image, it provides the Celery distributed asynchronous task queue/job system.

Support is included for downloading and installing requirements listed in requirements.txt and persisting these across container restarts.

Celery may be run in two modes, either worker or beat.

⁠Mirrors

⁠Conarx Containers

All our Docker images are part of our Conarx Containers product line. Images are generally based on Alpine Linux and track the Alpine Linux major and minor version in the format of vXX.YY.

Images built from source track both the Alpine Linux major and minor versions in addition to the main software component being built in the format of vXX.YY-AA.BB, where AA.BB is the main software component version.

Our images are built using our Flexible Docker Containers framework which includes the below features...

• Flexible container initialization and startup
• Integrated unit testing
• Advanced multi-service health checks
• Native IPv6 support for all containers
• Debugging options

⁠Community Support

Please use the project Issue Tracker⁠.

⁠Commercial Support

Commercial support for all our Docker images is available from Conarx⁠.

We also provide consulting services to create and maintain Docker images to meet your exact needs.

⁠Environment Variables

Additional environment variables are available from...

• Conarx Containers Postfix image⁠
• Conarx Containers Alpine image⁠

⁠CELERY_APP

Celery application, defaults to celery_app.celery_app.

⁠CELERY_INSTANCE_TYPE

Celery instance type, either worker (default) or beat.

⁠CELERY_LOG_LEVEL

Celery log level. eg. "debug"

⁠Volumes

⁠/app

Application directory.

⁠Files & Directories

⁠/app/requirements.txt

If /app/requirements.txt exists, pip will be used to install the relevant dependencies.

The virtual environment along with dependencies can be persisted using a volume for /var/www/virtualenv.

⁠/app/.venv/

Virtual environment for the application, it will be automatically created if it doesn't exist.

If it's been bind mounted as a volume, one can clear it out if required for it to be re-created on next container start.

⁠Health Checks

Health checks are done by the underlying images as Celery doesn't listen on any ports or provide any real sort of means to determine health.