Hi Daniel, On 2/14/19 5:57 AM, Daniel Ortega wrote: > > I think there is som confusion of what RUN in a Dockerfile does > > > I don't agree, my problem it's about something that is called "docker > builder" in Packer cannot be used to build anything (as I cannot > execute any "RUN" command). Maybe it's a semantic question. We use the Packer Docker builder on a daily basis to build containers for k8s and this works well for us so I think your stance is a bit strong :) > > So to produce a image that runs systemd do: > > a) shell provisioner to install systemd and services > b) change the ENTRYPOINT/CMD in changes to run systemd. > > > It's clear to me that using some provisioners you can do a workaround > for other cases, but I think that is *not for systemd*. AFAIK, > *systemd* should be the first daemon to start and the last daemon to > stop.
Do you have any evidence to support that claim? The 'first thing to start and last to stop' is from a runtime point of view when the container is running. When building, I think (but I have not tried) that what only matters is that you have systemd running. As Rickard said, let's see with your sample Dockerfile what you want to do. Vincent -- 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 packer-tool+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/ffb71f5f-0077-3afa-8ca5-0a73948649c4%40datameer.com. For more options, visit https://groups.google.com/d/optout.
