Adam Cameron
CMD export SOME_ENV_VAR=some_value
As opposed to just:
ENV SOME_ENV_VAR=some_value
In our Dockerfile we're chaining that export
with a call to start the actual process, eg:
CMD export SOME_ENV_VAR=some_value && supervisord -c /etc/supervisor/supervisord.conf
But pretty sure that doesn't make any difference to anything.
I guess the question is whether there's any difference in how an env variable gets set between ENV
and calling export
from the shell.