You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Try to "down" a compose over ssh will fail with V2 that worked in V1.
Can only recreated with -HOST and it need to be two or more services inside the compose (one services works)
.\docker-compose-v2.exe -H ssh://USER@docker-vm up -d && .\docker-compose-v2.exe -H ssh://USER@docker-vm down
Describe the results you received:
[+] Running 2/2
- Container composev2-busybox2-1 Started 1.2s
- Container composev2-busybox1-1 Started 2.8s
[+] Running 1/2
- Container composev2-busybox2-1 Removed 10.5s
- Container composev2-busybox1-1 Error while Removing 11.8s
error during connect: Delete "http://docker/v1.41/containers/9ec831308cba7cd8c68a698c7e1db9985974033918f58def885d18ba9b9059e4?force=1": command [ssh -l USER -- docker-vm docker system dial-stdio] has exited with exit status 1, please make sure the URL is valid, and Docker 18.09 or later is installed on the remote host: stderr=
The second Container is still there and not removed:
docker -H ssh://USER@docker-vm ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
5e4141ce6748 busybox "sleep 1d" 20 seconds ago Exited (137) 3 seconds ago composev2-busybox2-1
I tried it again with the current version and it still occurs with 2.3.3.
Same behavior as described above
Workaround is not to use the -Host-option but to pass the compose command with SSH
Before that the Compose file must be transferred to the VM and Compose must be present there.
Sorry i was wrong. I got the some error with 2.10.1
I think it has more todo with my SSH-Client / Server configuration then compose so i will leave the issue closed.
Switching to a tcp connection has fixed it for me.
-H tcp:// ...
Description
Try to "down" a compose over ssh will fail with V2 that worked in V1.
Can only recreated with -HOST and it need to be two or more services inside the compose (one services works)
Steps to reproduce the issue:
.\docker-compose-v2.exe -H ssh://USER@docker-vm up -d && .\docker-compose-v2.exe -H ssh://USER@docker-vm down
Describe the results you received:
The second Container is still there and not removed:
docker -H ssh://USER@docker-vm ps -a
Describe the results you expected:
Output from ComposeV1:
All Container are successfully removed
Additional information you deem important (e.g. issue happens only occasionally):
Output of
docker compose version
:Output of
docker info
:Additional environment details:
The text was updated successfully, but these errors were encountered: