docker-compose.yml pass true values as strings about supabase HOT 2 CLOSED

okay as you can see I run out of space. I am running the latest supabase commit,

this was exactly the error.

But I believe it is because I installed doing sudo apt install docker.io docker-compose instead of following this guide (https://docs.docker.com/engine/install/). I didn't followed this guide because I was using kali linux (in the example above), parrot and arch linux which none of them appear them as a installation.

Now I opened a new container with ubuntu and followed that guide to install docker.

But I believe that was the problem. In any case if you are using docker-compose instead of the new docker compose plugin you need to do what I said. Now I couldn't finish it at all because I run out of space. I also mounted up with docker-compose (in my kali machine), the interface worked and all the containers worked but I had more errors. And I tried removing the postgres from supabase and using my external one but I was having lot of problems too although I changed the wal_level and looked at the containers logs. Thanks

from supabase.

Thanks for opening.

• Can you explain the problem you had?
• Was an error printed when running the commands?
• What system are you running?
• Was it the latest commit?
• Is this using Docker or Orbstack or Podman or something else?

Docker Compose does support booleans (there are no official docs to say otherwise), it is only the YAML spec that requires specifying in case the parser has issues. In these cases, the keys are correct and picked up:

from supabase.