Encrypted environment variables question...

[mrapptambour]

In reference to 11. encrypted-aes:

Note - please forgive any docker ignorance that may follow here.

But...could one please explain why commands executed from codeship-steps.yml appear to have a different environment variable context as the same command executed from within a Dockerfile of the same step?

`
ADD check_for_foo.sh .

Why does this command fail and not contain CI* and FOO environment variables?

RUN ./check_for_foo.sh
`

Fork: https://github.com/mrapptambour/codeship-tool-examples/blob/master/11.encrypted-aes/Dockerfile

[mlocher]

Hey @mrapptambour,

with the support for build arguments (which was merged with moby/moby#15182) and released in v1.9.0 environment variables from the host aren't available during the build any longer.

We're working on supporting the Docker Compose v2 configuration file format, which will add support for build arguments to our Docker based platform as well.