<@U02Q3KHC59B> thanks for digging into #16166. I'm...
# developmentc
curved-television-6568
07/13/2022, 6:05 PM@sparse-lifeguard-95737 thanks for digging into #16166. I'm out traveling /wo my computer..
s
sparse-lifeguard-95737
07/13/2022, 6:07 PMyeah I saw the 🌴 no worries!
đź‘Ť 1
sparse-lifeguard-95737
07/13/2022, 6:08 PMif you have a minute:
was there an intent to have things like
{build_args.FOO}Dockerfilec
curved-television-6568
07/13/2022, 6:10 PMI'll likely have my 🌴 for quite some time due to relocation 🇸🇪=> 🇨🇦 but will be occasionally on a computer anyway at times.. ;)
đź‘Ť 1
s
sparse-lifeguard-95737
07/13/2022, 6:12 PMsafe travels!! quite an “exciting” time to be making a big move…
❤️ 1
âž• 1
c
curved-television-6568
07/13/2022, 6:12 PMUhm.. 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
sparse-lifeguard-95737
07/13/2022, 6:13 PM👍 my hypothesis for the bug is that we’re accidentally trying to interpolate the Dockerfile source. I’ll keep poking at it
đź’Ż 1
c
curved-television-6568
07/13/2022, 6:13 PMWe 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.
curved-television-6568
07/13/2022, 6:14 PMAnd in case of an address, replace it with the built image name
4 Views