`Error: no such option: -f`

lyssieth

Installed on an Arch system, Docker mono-container 1.2.0, followed this guide
My docker log is spammed full of this:

Error: no such option: -f
Usage: celery [OPTIONS] COMMAND [ARGS]...
Try 'celery --help' for help.

Error: no such option: -f
Usage: celery [OPTIONS] COMMAND [ARGS]...
Try 'celery --help' for help.

Error: no such option: -f
Usage: celery [OPTIONS] COMMAND [ARGS]...
Try 'celery --help' for help.

Error: no such option: -f
Usage: celery [OPTIONS] COMMAND [ARGS]...
Try 'celery --help' for help.

Usage: celery [OPTIONS] COMMAND [ARGS]...
Try 'celery --help' for help.

gcrk

Hello lyssieth and welcome to our forum!

First note, you shouldn't use the All-in-one or mono-container deploy method, its deprecated.

Besides this, it seems like you found a bug, I'll try to fix this as soon as possible. I guess for some reason its not supported anymore to have the options BEFORE the command, which is the reason for celery to fail to run. I will include a fix with 1.2.1.

gcrk

A new stable image is available on docker hub, could you try if your issue is fixed?

lyssieth

Different error this time.

Error: no such option: -A
You are using `-A` as an option of the worker sub-command:
celery worker -A celeryapp <...>

The support for this usage was removed in Celery 5.0. Instead you should use `-A` as a global option:
celery -A celeryapp worker <...>
Usage: celery worker [OPTIONS]
Try 'celery worker --help' for help.

I might try installing it the multi-container way, but Docker mono-container/AIO is just more comfortable for me since I plan to switch to a different OS on my server sometime next year (after upgrades).

gcrk

Thanks for reporting this back, I will fix this, too, hopefully tomorrow!

You can move the multi container setup much easier than the all-in-one container and there wont be updates for the AIO container in the future anymore, so I highly recommend not to use it for a fresh instance.

gcrk

Should be solved already using stable.