-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Python 3.8 support #5761
Comments
When running celery 4.4.0rc3 with python 3.8 and trying to deamonize during a docker startup script we get:
However once you remote into the docker and start it manually it works fine. |
so I actually solved this - just to let you know: If you run a docker wiht FROM python:3.8-buster and then you want to start the celeryd or celerybeat via a bash script in the start up process export COLUMNS=80 but maybe make the python processes have a default of 80 if it cannot read the terminal width for output formatting? |
I tracked down the Docker / Python 3.8 issue:
I'm unsure why |
@dalberto @rajwitt thanks for sharing the details of the root cause. I found this StackOverflow post that might be relevant. As far as I understand, the only reliable way to resolve this is by using the environment variable. |
We are being hit by this also. There are comments indicating that this may be an issue with Docker (although there are similarly also reports of people saying it is still an issue). Unfortunately, we are using an ancient version of Docker here ( |
If you are getting this error, it may be because you're allocating a pseudo-tty from docker. Here are some commands: No tty:
With tty:
In case you do need a tty, setting The tty size being |
Have the same issue on Setting this solves the problem
|
If this variable is not defined, Celery fails at startup. See celery/celery#5761
No description provided.
The text was updated successfully, but these errors were encountered: