Type generation with `--local` flag fails

[Bohooslav]

Affected area

Local development

Supabase CLI version

v2.107.9

Operating system

Fedora 44

Installation method

yarn

Command

npx supabase gen types --lang typescript --local --debug

Actual output

NotFound: FileSystem.readFile (/home/bohuslav/.supabase/profile)
NotFound: ChildProcess.spawn (docker container inspect supabase_db_kboom)

Expected behavior

Should generate types

Steps to reproduce

I use a local Supabase with Podman. All worked two weeks ago when I generated types the last time.

Crash report ID

No response

Docker and service versions

podman version 5.8.2

Additional context

No response

[mittal-parth]

Hey @Bohooslav

This has likely happened after 27b6af12, as part of the larger effort to port commands to native TS

Why it worked before: The Go CLI talked to containers via the Docker API client (respects DOCKER_HOST), so Podman worked without a docker binary on PATH - as long as the Podman socket was configured.

Why it fails now: The native TS --local path runs docker container inspect and docker run as subprocesses. Your error means the docker executable isn’t on PATH.

Can you try this:

• Install a Docker CLI shim for Podman (on Fedora: sudo dnf install podman-docker) or ensure docker is on PATH and can talk to Podman
• ensure the local stack is running (supabase start),
• then try re-runing supabase gen types --local.

[Bohooslav]

Yes, installing podman-docker worked!

Now waiting for proper fix 🙃

[mittal-parth]

@jgoux two ways to do this:

1. Add a shared helper that resolves CLI: docker on PATH → else podman → else fail with a clear message. Use that binary for all inspect / run subprocesses. Will work for podman only setups
2. gen types doesn't use the LegacyDockerRun service. We can make it use that instead of the direct docker subprocess logic. Won't fix podman by itself but atleast the UX will be clear, with parity mantained with other commands like db dump

thoughts?

[Bohooslav]

I'd personally go for option 1. Get rid of legacy; build the next-gen helper.