kierenevans
commented
7 years ago Hey @richdynamix,
To affect variables during the build stage, you'll need to pass GITHUB_TOKEN and DEVELOPMENT_MODE in as ARGs in the Dockerfile, with appropriate changes to the docker-compose.yml (and continuous-pipe.yml if being used) to pass the variables through in the build section.
Note that this will make the token part of the history of the image (fetchable with docker history --no-trunc <image>), so please ensure you are pushing to a private docker repository.
I don't think that confd will be running during the build of the image unless you were to override a function to call it, for example:
alias_function do_build do_project_build_inner
function do_build() {
do_templating
do_project_build_inner
}in your plan.sh file.
I hope this helps!
richdynamix
sroze
I don't think I am doing anything wrong, just what I am used to doing but anything I set in
environmentofdocker-compose.ymlis not being picked up when I have a composer project.For example. I am setting
DEVELOPMENT_MODEandGITHUB_TOKENbut these aren't being picked up when the container is being built.docker-composerDockerfile-When I run this I get the following during composer install -
Which illustrates that the
DEVELOPMENT_MODEandGITHUB_TOKENare not read as the composer flags are not applied and theGITHUB_TOKENis missing from the condition.If I remove the
composer.jsonfile from the project and just build the container with no install it starts fine and I can echo out the variables in the container -Strangely enough, the
.envfile that I have setup to be generated with the confD templates is not generated unless thecomposer.jsonfile is missing.It must be a configuration issue on my side but I can't see what could cause this. Any ideas would be greatly appreciated.