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
When I run compose.bat from the PATH I got: .local/share/containers/podman-desktop/extensions-storage/podman-desktop.compose/bin/compose.bat up -d 'docker-compose' is not recognized as an internal or external command, operable program or batch file.
I am trying to use podman desktop's compose integration and spin up some example application (awesome-docker/flask).
It might be either bug or I missed the concept how it works, I tried to follow the compose installation process.
Have podman desktop running, podman installed and running
Install compose via Compose download button
Make it system wide installation
Add installation folder to on the PATH
Restart the podman desktop
For quite a time I see a warning by compose button in status bar stating something like: No running container engine. Unable to write a compose wrapper script that will set DOCKER_HOST in that case. Please start a container engine first.
If I wait a long enough or restart compose extension (disable-enable) I will get: Compose is installed and usable with C:\Users\Ondrej\.local\share\containers\podman-desktop\extensions-storage\podman-desktop.compose\bin\compose
I expect to work now on CLI with a docker-compose which should be on a PATH, so I try: $ docker-compose up -d Cannot connect to the Docker daemon at npipe:////./pipe/docker_engine. Is the docker daemon running?
Which leads me to the trying of the compose.bat executable on CLI which should be at the same folder as installed docker-compose.exe:
$ ./../../../.local/share/containers/podman-desktop/extensions-storage/podman-desktop.compose/bin/compose.bat up -d
'docker-compose' is not recognized as an internal or external command,
operable program or batch file.
I am not sure If there is a bug in the compose.bat script, docs/guide is misleading, I am doing something wrong.
Operating system
Windows 10 Professional
Installation Method
None
Version
1.2.1
Steps to reproduce
No response
Relevant log output
No response
Additional context
There is a warning in podman desktop for docker socket compatibility in podman desktop: ⚠ Docker Socket Compatibility: Docker socket is not reachable. Docker specific tools may not work.
The text was updated successfully, but these errors were encountered:
I'm going to close this issue for now as we are going to update the Windows documentation via the issue #3557 (this issue is duplicated here and #3557).
Bug description
When I run
compose.bat
from thePATH
I got:.local/share/containers/podman-desktop/extensions-storage/podman-desktop.compose/bin/compose.bat up -d 'docker-compose' is not recognized as an internal or external command, operable program or batch file.
I am trying to use podman desktop's compose integration and spin up some example application (awesome-docker/flask).
It might be either bug or I missed the concept how it works, I tried to follow the compose installation process.
No running container engine. Unable to write a compose wrapper script that will set DOCKER_HOST in that case. Please start a container engine first.
Compose is installed and usable with C:\Users\Ondrej\.local\share\containers\podman-desktop\extensions-storage\podman-desktop.compose\bin\compose
PATH
, so I try:$ docker-compose up -d Cannot connect to the Docker daemon at npipe:////./pipe/docker_engine. Is the docker daemon running?
compose.bat
executable on CLI which should be at the same folder as installeddocker-compose.exe
:I am not sure If there is a bug in the
compose.bat
script, docs/guide is misleading, I am doing something wrong.Operating system
Windows 10 Professional
Installation Method
None
Version
1.2.1
Steps to reproduce
No response
Relevant log output
No response
Additional context
There is a warning in podman desktop for docker socket compatibility in podman desktop:
⚠ Docker Socket Compatibility: Docker socket is not reachable. Docker specific tools may not work.
The text was updated successfully, but these errors were encountered: