Created
July 27, 2016 11:24
-
-
Save toddlers/d57565644d860160c05fcb4364dbd16c to your computer and use it in GitHub Desktop.
using envsubst in Dockerfile
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
FROM ubuntu:trusty | |
RUN \ | |
apt-get update \ | |
&& apt-get -y install gettext-base \ | |
&& apt-get clean \ | |
&& rm -rf /var/lib/apt/lists/* | |
ENV VALUE=foo | |
ENV VALUE1=boo | |
COPY config.txt source_config.txt | |
RUN envsubst < "source_config.txt" > "config.txt" |
I don't think you'd be able to
RUN
the envsubst. Well I mean you can run it, but it won't have the environment variables that are passed when the container is launched, which is probably what you'd want otherwise you should use build args. Maybe you meanCMD
on that last line instead ofRUN
?
lol man :)
You can run it, but must have it in the same line - so they will be in the same context.
RUN export VALUE=foo && \
export VALUE1=$(cmd to get value1) && \
envsubst < "source_config.txt" > "config.txt"
Update available packages in Debian
RUN apt-get update
CMD export VALUE=foo &&
export VALUE1=$(cmd to get value1) &&
envsubst < "source_config.txt" > "config.txt"
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I don't think you'd be able to
RUN
the envsubst. Well I mean you can run it, but it won't have the environment variables that are passed when the container is launched, which is probably what you'd want otherwise you should use build args. Maybe you meanCMD
on that last line instead ofRUN
?