I am trying to pass some Prisma config as environment variable PRISMA_CONFIG when I start my Docker container (see image). Can’t get my head around why I am getting the following parse error: “Unable to load Prisma config: mapping values are not allowed here”. Any ideas?

Probably wrong identation or hierarchy in your config file. Can you share it?

I think you are missing some spaces before

connector

this is the content I used as a base

maybe this helps as well: https://www.prisma.io/forum/t/in-docker-compose-why-is-the-value-of-prisma-config-prefixed-by-a-pipe/3568/3?u=nilan

Thanks, ended up in that post a couple of times while googling.. That is when using a yml file and not passing it as an inline variable - right?

I don’t know off the top of my head if the yml parser in prisma also recognizes tabs, but you can try by just replacing the space identation with \t (to rule out identation issues)

@dpetrick thanks but still getting the same error

Looking closer, docker -e has some issues iirc to pass escaped string sequences correctly to the container. I remember that there was an issue somewhere.

Ah, I see… Will try that! Was looking into that alternative a couple of hours ago. Thank you!

@Anton, this looks like an open feature request to me. Or did you actually use this parameter to make it work? What's the new command that you use?

Correct.. I accidentally linked to a specific comment. My intention was to link to the issue in general. I tried the parameter but it didn’t work either… So, no solution yet.

@Anton check https://www.prisma.io/forum/t/starting-prisma-service-with-a-dockerfile-instead-of-docker-compose-yml/4141/3?u=nilan

@nilan Thanks! Will try that out when I have time but looks promising for sure 🙂