Cannot stop Docker Compose application. Reason: exit status 1

[QuAzI]

Some docker containers runs from docker-compose.yml I can stop them one by one from menu but can't stop all from one group. Looks like docker compose stop fired in wrong directory and have to be fired in the same directory where docker-compose.yml placed. Take dir for first container in group

docker inspect 1c84e69c1947 --format '{{ index .Config.Labels \"com.docker.compose.project.working_dir\" }}'

and use it to exec docker compose whatever

[klodoma]

I can confirm this. This is an issue since a long time.

[akulov]

I have this issue also

[blechema]

Confirmed for Docker Desktop 4.13.1 (90346)

[manodupont]

+1

[katipierson]

1 - after fresh update

[zvillon]

Same thing here, can't start or stop all of them at the same time, but one by one it works perfectly fine

[ChrisKulesza]

Confirmed for Docker Desktop 4.13.1 (90346)

+1

[slowpokefarm]

Same issue on MacOS version

[blechema]

Confirmed for new Version 4.14.0 (91374) as well

[romanvincit]

Same problem here, MacOS. Docker Desktop 4.14.0 (91374).

[QuAzI]

Looks like it works in 4,14 but... You have to enable "Use Docker Compose V2" before container created.

[slowpokefarm]

Looks like it works in 4,14 but... You have to enable "Use Docker Compose V2" before container created.

Doesn't exactly sounds like "works" then. What if you don't use V2? Or if you don't have the option to recreate a container? This is a regression and there's no reason to close this issue as solved.

[akulov]

Looks like it works in 4,14 but... You have to enable "Use Docker Compose V2" before container created.

Doesn't exactly sounds like "works" then. What if you don't use V2? Or if you don't have the option to recreate a container? This is a regression and there's no reason to close this issue as solved.

Agree with you. We use composer v1 in our project

[adentya]

Same problem here. I downgraded to 4.12.0 and it works as before.

https://docs.docker.com/desktop/release-notes/#docker-desktop-4120

[som-sama]

+1 facing the same issue

[ljo123]

Still having this issue with docker compose v2 enabled.

[CPoncet]

I encountered this issue when trying to stop/delete a group of containers.

Had to stop/delete containers one by one.

[spake-xx]

+1 having exactly same issue. Never touched docker-compose v2 and my docker containers just stopped working. But works like a charm starting and stopping one by one.

[som-sama]

Guys, I found a solution. I you are on mac the air play uses the 5000 port due to which this issue arise. I stopped the airplay and after that, this issue got solved. Checkout this link to understand better.

https://developer.apple.com/forums/thread/682332

[ter1203]

Same here. succeed on docker compose but it is getting error. was working fine till yesterday...

[nerdess]

Same issue here

[KobeNorris]

Same issue here, but I am using Windows, and it works fine with 4.11 version but was trapped in this error with 4.15

[vittoriodev]

Same +1

[blechema]

Confirmed for new version 4.15.0 (93002) as well

[blechema]

Confirmed for new version 4.16.1 (95567) also

[skye-harris]

Confirming affected also on latest version. Downgrading to 4.11 restored functionality

[rajibbinalam]

same issue on my pc. v4.15.0

[rajibbinalam]

same issue on my pc. v4.15.0

[ArvisCe]

Happened to me after changing permissions to all files in folder. Changing them back fixed it.

[jjphung]

Same issue for Docker Desktop Mac 4.16.2, Docker version 20.10.22 build 3a2c30b, Docker Compose version v2.15.1.

Containers just stop working if restarting and hangs.

Fixable with an engine restart or killall command.

[hashs42]

Had same issue in v4.15.0 - got it solved after updating to v4.17.0 Running M1 MacOS Ventura

[DiegoTavelli]

updated from v4.15 to 4.17 and problem solved.

[katipierson]

Not for me. Problem still remains. "Exit status 1". OS: Windows 10, Stack deleted and new build. Installed Dockerversion: 4.17.0 (99724)

[klodoma]

I confirm this also working on 4.17.0. Running on Windows 11.

[indovsky]

Same problem in version 4.18. "Use Docker Compose V2" fixed the issue

[zsimuno]

Still having this issue on 4.18

"Use Docker Compose V2" is already enabled for me. One time this happened I rebuilt the images but it happened again and I don't like the idea rebuilding images every time this happens.

Any new fixes for this?

[Sammeeey]

Same, after my container didn't start properly (as it usually does).

Got this error when I tried to stop sub containers: Error invoking remote method 'docker-stop-container': Error: (HTTP code 500) server error - cannot stop container: ...: tried to kill container, but did not receive an exit event

Eventually restarted Docker (didn't solve problem):

Even stopped Docker in the task manager after seeing Turning off the Docker Engine for 3 minutes. Then started Docker again. Had the same text again. Stopped the task again. Had to wait for Starting the Docker Engine another 5 minutes...

Now restarting my PC and hoping that it works then again... Seems to work as usual after restarting my PC and running the Docker and container startup as usual.

[austinarchibald]

I'm having this occur once every 2 days. Running about 10 containers on Docker Desktop Mac. Cannot connect to the web guis, docker says they're "running" but they're basically dead. Cannot restart, getting the 500 server error. Only thing that seems to work is a hard reboot of my computer. This is getting very annoying. Not sustainable. Do I need to move everything to a linux server?!

[nowshadk07]

Cannot stop Docker Compose application. Reason: compose [stop] exit status 1. request returned Internal Server Error for API route and version / Some URL / check if the server supports the requested API version

[neldivad]

Did a complete reinstall of Docker and was able to run and stop my containers. After restarting Windows I run into the same issue. Unable to start Docker or close Docker.

[lkjimy]

Got the same issue. It was working perfectly fine before. Updated docker desktop a few times already, still getting this issue. I don't remember in which version the issue started. I'm currently running version 4.26.1 (131620).

I thought the resource saver feature was causing it, since I would leave idle for some time, and my service would stop working, but it also didn't solve the issue...

I'm not using WSL

Having to completely restart docker, every time this happens, and it happens a lot.

I'm avoiding doing a full uninstall and reinstall, because I would have to backup a bunch of volumes and redo a bunch of configs from scratch...

Also...

1. One of the recent updates removed docker from my env, so, I had the manually put it back to get docker CLI working again.
2. Every update has this annoying issue where it gets stuck mid update (creating user group or something), so I have to force kill the installation, restart the computer, download the update manually, and run it again.

[lkjimy]

Did a full uninstall and reinstall of 4.27.1 and the issues persisted. Upgraded to 1.28.0 now, and still getting the same problem. What are the chances of this being a Windows issue? Something related to memory management? This is getting very frustrating. Was anybody able to figure out what is happening?

[1stGGMan]

Same issue on 4.31.1 (HTTP code 500) server error - Cannot restart container beb059a150380d95895f1a0c605e488a50afadc0791079fbeea9ead091654d48: tried to kill container, but did not receive an exit event

[niranjanakella]

A simple docker-compose down worked for me.

[j-suhas]

Confirmed for Docker Desktop 4.27.2 and Docker Engine 25.0.3