Jump to solution
Verify

Celery Dockerfile - Build failed with kombu<5.0,>=4.6.4 installation (Fix)

Fixed
Spec
Package
Celery
Fixed In
4.4.0rc5
Python
3.4
Verdict
Status
Fixed
Safe for prod
No
Risk
Low
Last verified
2026-02-09
Own content ratio
0.24
#5763 ai caching crash dns duplicates llm Updated: 2026-02-13
Issue #5763

The Fix

pip install celery==4.4.0rc5

Based on closed celery/celery issue #5763 · PR/commit linked

Production note: This usually shows up under retries/timeouts. Treat it as a side-effect risk until you can verify behavior with a canary + real traffic.

Jump to Verify Open PR/Commit
@@ -71,35 +71,35 @@ RUN pyenv exec python2.7 -m pip install --upgrade pip setuptools && \ # Setup one celery environment for basic development use RUN pyenv exec python3.8 -m pip install \ - -r requirements/default.txt \ + -r requirements/dev.txt \ -r requirements/test.txt \
repro.py
Building celery Step 1/26 : FROM debian:buster ---> 8e9f8546050d Step 2/26 : ENV PYTHONIOENCODING UTF-8 ---> Using cache ---> d203357ee575 Step 3/26 : RUN apt update && apt install -y build-essential libcurl4-openssl-dev libffi-dev tk-dev xz-utils curl lsb-release git libmemcached-dev make liblzma-dev libreadline-dev libbz2-dev llvm libncurses5-dev libsqlite3-dev wget pypy python-openssl libncursesw5-dev zlib1g-dev pkg-config libssl1.0-dev ---> Running in 997e518d0344 WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Get:1 http://security-cdn.debian.org/debian-security buster/updates InRelease [39.1 kB] Get:2 http://cdn-fastly.deb.debian.org/debian buster InRelease [122 kB] Get:4 http://security-cdn.debian.org/debian-security buster/updates/main amd64 Packages [108 kB] Get:3 http://cdn-fastly.deb.debian.org/debian buster-updates InRelease [49.3 kB] Get:5 http://cdn-fastly.deb.debian.org/debian buster/main amd64 Packages [7899 kB] Get:6 http://cdn-fastly.deb.debian.org/debian buster-updates/main amd64 Packages [5792 B] Fetched 8222 kB in 14s (580 kB/s) Reading package lists... Building dependency tree... Reading state information... All packages are up to date. WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Reading package lists... Building dependency tree... Reading state information... Package libssl1.0-dev is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'libssl1.0-dev' has no installation candidate ERROR: Service 'celery' failed to build: The command '/bin/sh -c apt update && apt install -y build-essential libcurl4-openssl-dev libffi-dev tk-dev xz-utils curl lsb-release git libmemcached-dev make liblzma-dev libreadline-dev libbz2-dev llvm libncurses5-dev libsqlite3-dev wget pypy python-openssl libncursesw5-dev zlib1g-dev pkg-config libssl1.0-dev' returned a non-zero code: 100
verify
Re-run the minimal reproduction on your broken version, then apply the fix and re-run.
fix.md
Option A — Upgrade to fixed release\npip install celery==4.4.0rc5\nWhen NOT to use: This fix is not applicable for environments using Python versions other than 3.4.\n\n

Why This Fix Works in Production

  • Trigger: ---> Running in a29a6ca1238a
  • Mechanism: Updated the Docker configuration to resolve build issues related to kombu version requirements.
  • Why the fix works: Updated the Docker configuration to resolve build issues related to kombu version requirements. (first fixed release: 4.4.0rc5).
Production impact:
  • If left unfixed, the same config can fail only in production (env differences), causing startup failures or partial feature outages.

Why This Breaks in Prod

  • Shows up under Python 3.4 in real deployments (not just unit tests).
  • Surfaces as: ---> Running in a29a6ca1238a

Proof / Evidence

  • GitHub issue: #5763
  • Fix PR: https://github.com/celery/celery/pull/5801
  • First fixed release: 4.4.0rc5
  • Reproduced locally: No (not executed)
  • Last verified: 2026-02-09
  • Confidence: 0.95
  • Did this fix it?: Yes (upstream fix exists)
  • Own content ratio: 0.24

Discussion

High-signal excerpts from the issue thread (symptoms, repros, edge-cases).

Jump to Sources Open on GitHub
“@thedrow @auvipy are you able to setup the docker based development environment? is docker build successfully for you? Very basic checkout the master code and…”
@naggappan · 2019-10-07 · source
“@thedrow Any update on this? Facing the same issue here when building via docker. !image”
@dipAch · 2019-10-23 · source
“PR in progress https://github.com/celery/celery/pull/5801”
@auvipy · 2019-10-29 · source
“technically, dev environment should be based on master”
@auvipy · 2019-10-29 · source

Failure Signature (Search String)

  • ---> Running in a29a6ca1238a

Error Message

Stack trace
error.txt
Error Message ------------- ---> Running in a29a6ca1238a --2019-10-30 18:22:03-- http://packages.couchbase.com/clients/c/libcouchbase-2.10.4_buster_amd64.tar Resolving packages.couchbase.com (packages.couchbase.com)... 54.230.195.161, 54.230.195.18, 54.230.195.155, ... Connecting to packages.couchbase.com (packages.couchbase.com)|54.230.195.161|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2019-10-30 18:22:04 ERROR 404: Not Found. tar: libcouchbase-2.10.4_buster_amd64.tar: Cannot open: No such file or directory tar: Error is not recoverable: exiting now dpkg: error: cannot access archive 'libcouchbase-2.10.4_buster_amd64/libcouchbase2-core_2.10.3-1_amd64.deb': No such file or directory dpkg: error: cannot access archive 'libcouchbase-2.10.4_buster_amd64/libcouchbase-dev_2.10.3-1_amd64.deb': No such file or directory ERROR: Service 'celery' failed to build: The command '/bin/sh -c sh install-couchbase.sh' returned a non-zero code: 2

Minimal Reproduction

repro.py
Building celery Step 1/26 : FROM debian:buster ---> 8e9f8546050d Step 2/26 : ENV PYTHONIOENCODING UTF-8 ---> Using cache ---> d203357ee575 Step 3/26 : RUN apt update && apt install -y build-essential libcurl4-openssl-dev libffi-dev tk-dev xz-utils curl lsb-release git libmemcached-dev make liblzma-dev libreadline-dev libbz2-dev llvm libncurses5-dev libsqlite3-dev wget pypy python-openssl libncursesw5-dev zlib1g-dev pkg-config libssl1.0-dev ---> Running in 997e518d0344 WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Get:1 http://security-cdn.debian.org/debian-security buster/updates InRelease [39.1 kB] Get:2 http://cdn-fastly.deb.debian.org/debian buster InRelease [122 kB] Get:4 http://security-cdn.debian.org/debian-security buster/updates/main amd64 Packages [108 kB] Get:3 http://cdn-fastly.deb.debian.org/debian buster-updates InRelease [49.3 kB] Get:5 http://cdn-fastly.deb.debian.org/debian buster/main amd64 Packages [7899 kB] Get:6 http://cdn-fastly.deb.debian.org/debian buster-updates/main amd64 Packages [5792 B] Fetched 8222 kB in 14s (580 kB/s) Reading package lists... Building dependency tree... Reading state information... All packages are up to date. WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Reading package lists... Building dependency tree... Reading state information... Package libssl1.0-dev is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'libssl1.0-dev' has no installation candidate ERROR: Service 'celery' failed to build: The command '/bin/sh -c apt update && apt install -y build-essential libcurl4-openssl-dev libffi-dev tk-dev xz-utils curl lsb-release git libmemcached-dev make liblzma-dev libreadline-dev libbz2-dev llvm libncurses5-dev libsqlite3-dev wget pypy python-openssl libncursesw5-dev zlib1g-dev pkg-config libssl1.0-dev' returned a non-zero code: 100

Environment

  • Python: 3.4

What Broke

Docker build fails, preventing the setup of the development environment.

Fix Options (Details)

Option A — Upgrade to fixed release Safe default (recommended)

pip install celery==4.4.0rc5

When NOT to use: This fix is not applicable for environments using Python versions other than 3.4.

Use when you can deploy the upstream fix. It is usually lower-risk than long-lived workarounds.

Fix reference: https://github.com/celery/celery/pull/5801

First fixed release: 4.4.0rc5

Last verified: 2026-02-09. Validate in your environment.

Get updates

We publish verified fixes weekly. No spam.

Subscribe

When NOT to Use This Fix

  • This fix is not applicable for environments using Python versions other than 3.4.

Verify Fix

verify
Re-run the minimal reproduction on your broken version, then apply the fix and re-run.

Did This Fix Work in Your Case?

Quick signal helps us prioritize which fixes to verify and improve.

Prevention

  • Capture the exact failing error string in logs and tests so you can reproduce via a minimal script.
  • Pin production dependencies and upgrade only with a reproducible test that hits the failing path.

Version Compatibility Table

VersionStatus
4.4.0rc5 Fixed

Related Issues

No related fixes found.

Cluster: celery:configuration-error Celery hub Celery best practices All hubs All clusters
Related clusters: Data consistency Duplicates Duplicate processing

Sources

We don’t republish the full GitHub discussion text. Use the links above for context.

Source & Disclaimer: Analysis derived from GitHub Issue #5763. Not affiliated with the library maintainers. Verify before production use.