search

aschmelyun / docker-compose-wordpress

A docker-compose workflow for local WordPress development
241 stars 151 forks source link

wp-cli exited (0) #4

Open daqarash opened 3 years ago

daqarash commented 3 years ago

Hi there!

I am using this repo. for my local dev setup. Somehow I run into this issue where wp-cli shows (grey icon showing the container is not running. It says EXITED (0).)

If I remove the wp-cli container everything else works fine.

Screenshot: image

When I click the wp-cli container to see the logs show this image

I appreciate it if you could help.

daqarash commented 3 years ago

Hi there!

I am using this repo. for my local dev setup. Somehow I run into this issue where wp-cli shows (grey icon showing the container is not running. It says EXITED (0).)

If I remove the wp-cli container everything else works fine.

Screenshot: image

When I click the wp-cli container to see the logs show this image

I appreciate it if you could help.

In addition to that I tried to run this command I found on the official page wp-cli.org "PHP wp-cli.phar --info"

image

I then tried to run "docker-compose wp --rm wp user list" image

It shows results. Am kinda confused.

johnfmorton commented 3 years ago

This isn't my repo, but I think the behavior you described initially is what is expected. It's what I see on my end and I would say it's working correctly.

The Docker dashboard shows the grayed out CLI container on purpose. There is no reason to have it active all the time using resources. When you run the command...

docker-compose run --rm wp user list

It runs the container with the --rm flag which will shut it back down after successfully executing the command. The next time you need to execute something from the wp-cli, you just run the docker-compose run --rm wp COMMANDSHERE and it will reactivate the container, execute your function, and then exit again.

daqarash commented 3 years ago

This isn't my repo, but I think the behavior you described initially is what is expected. It's what I see on my end and I would say it's working correctly.

The Docker dashboard shows the grayed out CLI container on purpose. There is no reason to have it active all the time using resources. When you run the command...

docker-compose run --rm wp user list

It runs the container with the --rm flag which will shut it back down after successfully executing the command. The next time you need to execute something from the wp-cli, you just run the docker-compose run --rm wp COMMANDSHERE and it will reactivate the container, execute your function, and then exit again.

Thanks John ✌️