fix(docker): fix passing env vars to running shell

[laurentlp]

This PR fixes an issue where environment variables were not passed to the shell when starting the Docker container. To fix the issue, we now propagate the env vars so that a user starting the container with -e arguments will see his variables passed to the Botpress binary.

[EFF]

seems good to me, I assume you tested and works.

[slvnperron]

@sebburon @bassamtantawi-botpress @davidvitora given the history of this one 😆 can you guys please have a look at this

[davidvitora]

Container failed when running with

sudo docker run -d \
--name=container_name \
-p 3000:3000 \
ghcr.io/botpress/botpress/server:llp_fix_docker_image_env_vars \
bash -c "./duckling & ./bp --auto-migrate"

I got an error when running creating the container; I am using my old command to execute Botpress

[davidvitora]

After the latest changes, it's working correctly

[sebburon]

Currently testing this on an AWS Hosted cluster.
I will update this when I'm done later today

[bassamtantawi-botpress]

it is working for me too

[sebburon]

Tested on AWS and it works