ps: unrecognized option: p

[iVegas]

I'm using the https://github.com/resque/php-resque library on the project. So there is a worker script handling single/multiple php processes.

docker-compose exec php bash -c 'REDIS_BACKEND=redis:6379 QUEUE="*" COUNT=2  vendor/bin/resque'

So the problem is when trying to stop the process of that script then the error messages related to the BusyBox appeared (or nothing happened and looks like the process become frozen). This is the easiest scenario that can be reproduced. There also some scenarios which break the work of processing of the Drupal kernel in the script app. But it hard to reproduce and I'm not sure that I can provide many details regarding those cases.

See the log of the php container right after an attempt to stop the script:

[notice] Shutting down
[notice] Shutting down
ps: unrecognized option: p
ps: unrecognized option: p
BusyBox v1.31.1 () multi-call binary.

Usage: ps [-o COL1,COL2=HEADER]

Show list of processes

        -o COL1,COL2=HEADER     Select columns for display

After some googling I found related issues. Here is one of them rmohr/docker-activemq#40 . Hope this will help.
Also tried to perform those scenarios using other php images (like https://hub.docker.com/r/devwithlando/php) and those issues stopped to appear.

Thanks

[csandanov]

ps in alpine is a part of busybox, hence implements a limited number of options, maybe installing procps from alpine package can help. Anyway, not wodby/php issue at all

[iVegas]

Can be somehow defined by some environment variable this package to install?

[csandanov]

no, we're not going to do that, especially for some project that as I understand not even designed to be run in docker