<@U02Q3KHC59B> thanks for digging into #16166. I'm...
# development
c
@sparse-lifeguard-95737 thanks for digging into #16166. I'm out traveling /wo my computer..
s
yeah I saw the 🌴 no worries!
👍 1
if you have a minute: was there an intent to have things like
{build_args.FOO}
interpolate correctly within the
Dockerfile
source? I can’t think of an easy way to make that work and not have it clash with Docker’s existing interpolation of env vars / build args
c
I'll likely have my 🌴 for quite some time due to relocation 🇸🇪=> 🇨🇦 but will be occasionally on a computer anyway at times.. ;)
👍 1
s
safe travels!! quite an “exciting” time to be making a big move…
❤️ 1
1
c
Uhm.. I don't think that interpolation is done “within” the Dockerfile. It should only be passed as —build-arg options to the docker build invocation.
s
👍 my hypothesis for the bug is that we’re accidentally trying to interpolate the Dockerfile source. I’ll keep poking at it
💯 1
c
We don't touch the source, only pass args.. the trick is for FROM instructions, whether it refers to a build arg that should be treated as a upstream target address or not.
And in case of an address, replace it with the built image name