Wrong path given by Doppler using docker-compose/Dockerfile

Need Help
1

Hi there,

We just started to try Doppler in my company to improve our secrets management :slight_smile:

No problem to setup envs, and first tokens to retrieve secrets.

However, when using

["doppler", "run", "--", "echo $PATH"]
The PATH I get is my host path and not the container path from the Dockerfile.

Consequences, it cannot find supervisord binary and configuration which are only available in the containers and not on my host filesystem.

If I try to run supervisord instead of echoing the PATH I get

| Doppler Error: fork/exec /usr/bin/supervisord -c /etc/supervisord.conf: no such file or directory

Am I missing something about PATH, binary management using doppler and docker/docker-compose ?

EDIT: I am sure supervisord and supervisord.conf are packed in the images I am starting with docker-compose. I did a manual check.

Best regards

2

Hi @Quentin_Cherifi!

Welcome to the Doppler Community!

The PATH inside your container should reflect the container path and not your local system path. Could you share your Dockerfile so I could attempt to reproduce this to see what’s going on for you?

Regards,
-Joel

3

Hey,

Thanks for your answer. Hmmm, I found a workaround, I don’t use supervisord and call directly php-fpm and it works.
For now, that works locally, but I will need to figure out why it’s not working properly with supervisord binary to eventually deploy on further environments.

Regards,

Quentin