Open rojinebrahimi opened 3 months ago
Hello! Hope everything is alright with you.
I had this problem with new version of Celery which forced me to use accept-content for de-serialization, Currently, I am using the Helm chart and I have added the command section to make it up & running:
command: - python - /app/cli.py - >- --accept-content=json,pickle,application/json,application/x-python-serialize
I thought it would be great to add this to the main Dockerfile so the image would be ready to use.
Moreover, I have made some changes in the main docker-compose.yml so that the image could be tested locally. Hope it helps others, too.
Your consideration is appreciated.
You can use the environment variable CE_ACCEPT_CONTENT I think. Can you give that a try?
https://github.com/danihodovic/celery-exporter/blob/master/src/cli.py#L43
Hello! Hope everything is alright with you.
I had this problem with new version of Celery which forced me to use accept-content for de-serialization, Currently, I am using the Helm chart and I have added the command section to make it up & running:
I thought it would be great to add this to the main Dockerfile so the image would be ready to use.
Moreover, I have made some changes in the main docker-compose.yml so that the image could be tested locally. Hope it helps others, too.
Your consideration is appreciated.