I'm using prisma with docker and I want to protect my service with managementApiSecret. Here is how my dockey-compose.yml looks like - http://prntscr.com/lfebga, it contains managementApiSecret but I keep getting warning

Warning: Management API authentication is disabled. To protect your management server you should provide one (not both) of the environment variables 'CLUSTER_PUBLIC_KEY' (asymmetric, deprecated soon) or 'PRISMA_MANAGEMENT_API_JWT_SECRET' (symmetric JWT).

. What's wrong?

That configuration looks correct to me, are you sure you applied it?

@dpetrick what do you mean by 'applied it'?

docker-compose up -d

after you changed the config, for example

Nope, I didn't do this. I thought docker does everything for me 😞

docker compose is nothing more than convenience for starting a bunch of containers. if you change the .yml you need to apply it again, else when would docker ever know when to apply it automatically? also, the snippet you now showed me is unrelated. you don’t need to use the

Dockerfile

if you use the compose file you showed me above. So which one is it?

@dpetrick aw, I'm completely noob in setting up Dokku and using Docker. I'm trying to set up dokku with prisma service and a server on graphql-yoga but I do not understand how to run it all inside the dokku. I followed this tutorial (and from it I get such Dockerfile) - https://www.prisma.io/docs/tutorials/deploy-prisma-servers/dokku-zie0ahhaox But it didn't work properly, so I added docker-compose.yml but haven't even run it. Now I'm completely confused with all of this. Could you, please, help me?

I have no experience with dokku. All I can give you is the following: If you want to run a docker image that has the config baked in and “just works” you can use the the snippet you send me, and use absolute paths for the config.

lemme try 🙂

I just tested a minimal example, the Dockerfile above works, the config I used is (with a mysql on my host system):

port: 4466
managementApiSecret: "somethingsomething"
enableManagementApi: "true"
databases:
  default:
    connector: "mysql"
    active: "true"
    host: "host.docker.internal"
    port: "3306"
    user: "root"
    password: "prisma"

docker build -t prismatest .

docker run -it -p 4466:4466 prismatest

-> localhost:4466/management is reachable

@dpetrick okay, so I finally deployed it all to the server but now I cannot deploy my prisma service, lol

Well, make sure the server is reachable and the docker bindings are set up in a way that you can access the container from the outside.

And here is what I get on deploying prisma service

The server is not reachable, you need to make sure to expose the server correctly with whatever dokku needs.

@dpetrick Not sure how to check it 😄 Maybe something wrong about running the command? Here is an output of running this command.

If you are still using the docker compose file above, then try the following port binding:

ports:
- "0.0.0.0:4466:4466"

@dpetrick still the same. Right now it used cache for this command

if you have shell access to the machine, see what the docker port bindings are saying

probably installed as root, fairly common.

sudo docker ps

yea, the caching probably caused the command to not be properly executed. You need to convince dokku to not use caches, if possible.