Good morning everyone, I'm trying to get GLUE tests running with Fixtures. I managed to create the fixtures but when I execute

APPLICATION_ENV=devtest vendor/bin/console queue:worker:start --stop-when-empty

I get the error

sh: 1: ps: not found

multiple times. I'm not sure what this means and how to figure it out so my question is: Can you guys help me with this?

Do you execute the console command outside of the docker container or within? What OS do you use locally? Background of the question is that the console worker tries to execute the tool ps which gives back what processes are running on unix systems. If you would execute the command above on a windows system it would fail, as windows to my knowledge does not have a "ps". That's just a guess what the error could be.

I'm on linux (Ubuntu) and execute the command inside the php-cli container

Docker containers from spryker come in two flavours, alpine or debian slim. Alpine comes with "ps" pre installed in debian slim I'm not sure as debian has a separate package for "ps" (called procps). You could do an

docker/sdk cli which ps

to find out if the package is installed. If not I suggest open a bug report on spryker side (https://spryker.force.com/support/s/)

We're actually not using docker/sdk for now but the command should then look like this for me:

docker-compose exec php-cli bash -c "which ps"

, right? => This command doesn't give any output If I execute it on the host directly I get

/usr/bin/ps

So if I understood you correctly it is the "required" ps, isn't it?

The container name would be <projectname>_cli_1 if you use the standard spryker container stack. If you build your docker stack on your own the answer is yes, ps is required to run spryker.

Ok, thank you very much for your input. This seems to be an issue on our side then.

@rough-scientist-68683 BTW why don't you use

docker/sdk

tool?

As far as I know we're investigating if we can use it with our docker-stack. So it's just a question of time.

We did the migration a few weeks ago (or months?) and ended up in forking it because we had the need for additional containers and removed the ELK stack (we use fact finder). @square-laptop-25127 If adding containers & removing unnecessary ones would be possible we would be much happier with the docker/sdk as it is working pretty well for us. But without this features we are only partially satisfied as forking and keeping docker/sdk up to date on our own is not trivial and takes a lot of time, especially when considering how fast docker/sdk is evolving (apparently a good thing). -> I interpreted your questions that you would love to get some feedback on the docker/sdk 😉

@plain-barista-64036 is happy about any feedback regarding docker/sdk in this case.

@wooden-king-30682 thanks again for your comment. It took me a while to really understand what you were saying but now the error is gone. I needed to install procps in the php-cli docker container for the command to run properly. THANK YOU

Thank you guys for your feedback. I am carefully collecting all your comments and thoughts, and we are considering them when planning next releases/features.