Unless I'm wrong, there is no way that I can see to use source a packer-built Docker image from two upstream images, so my "best bet" isn't really an option.
On Tuesday, April 28, 2020 at 2:42:48 PM UTC-7, G. Richard Bellamy wrote: > > The current methodology for injecting metadata into a Docker image is via > "changes:[]", which is then used via "docker commit --change". > > Because "docker commit --change" doesn't support STOPSIGNAL, neither does > the current implementation of the packer Docker builder. > > I'm struggling with the proper methodology for this. On the one hand, I > could create a base image using a Dockerfile, which is probably my current > best bet. Or I could do signal handling in my ENTRYPOINT, which seems > irrational as there's STOPSIGNAL for exactly that purpose. > > Any guidance or suggestions are greatly appreciated! > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/packer/issues IRC: #packer-tool on Freenode --- You received this message because you are subscribed to the Google Groups "Packer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/811e94f7-9ad6-429e-8388-a37a17f939c3%40googlegroups.com.
