I have installed the Astro CLI on a Windows 10 machine with WSL2 and Podman Desktop 4.6.2. Podman works fine as it is run other containers. It also runs the Postgres container. After having followed the Astro CLI (9.1.0) installation instructions, ‘astro dev init’ works fine (packages.txt is empty though), however commands like ‘astro dev start’ and ‘astro dev ps’ return the following message: time=“2023-09-26T11:56:14+02:00” level=fatal msg=“error init compose client protocol not available”
No new images or containers show up in Podman for the webserver, etc.
Any suggestions please? As a workaround, can I start the services individually in Podman?
Hey @patricm! Thanks for reaching out here, and welcome to Astro. Love that you’re using the Astro CLI, though sorry to hear you’re having trouble.
If Podman is running fine on other containers, you may just need to configure the Astro CLI to actually “know” to use Podman instead of our Docker default.
Running ‘astro --verbosity debug’ just brings up the available commands. I have appended the flags to the commands instead. No additional info is displayed though…
PS C:\Users\pat\astrotest> astro config set -g container.binary podman
Setting container.binary to podman successfully
PS C:\Users\pat\astrotest> astro config set -g duplicate_volumes false
Setting duplicate_volumes to false successfully
PS C:\Users\pat\astrotest> astro version --verbosity debug
Astro CLI Version: 1.19.2
PS C:\Users\pat\astrotest> astro dev ps --verbosity debug
time=“2023-11-03T11:19:15+01:00” level=fatal msg=“error init compose client protocol not available”
Also retried the initialization…
PS C:\Users\pat\astrotest> astro dev init --verbosity debug
Initializing Astro project
Pulling Airflow development files from Astro Runtime 9.4.0
C:\Users\pat\astrotest
You are not in an empty directory. Are you sure you want to initialize a project? (y/n) y
Reinitialized existing Astro project in C:\Users\pat\astrotest
PS C:\Users\pat\astrotest> astro dev start --verbosity debug
time=“2023-11-03T11:26:25+01:00” level=fatal msg=“error init compose client protocol not available”
I am not sure that this will help but since you are on Podman 4 your duplicate_volumes should not be false. Maybe try setting it to true:
astro config set -g duplicate_volumes true
Also is your DOCKER_HOST environment variable set to the location of your Podman service socket? If not you can get more information on how to do this here.
We are in the process of trying to reproduce the error you are receiving any information about your environment would be helpful.
Hey,
We are facing the same issue, when trying to start the astro project on a Windows server with podman installed. Could you please help us in resolving this.
level=fatal msg=“error init compose client ssh host connection is not valid: extra path after the host: "/run/user/1000/podman/podman.sock"”