Hi Rickard, On 2/12/19 11:48 AM, Rickard von Essen wrote: > I think there is som confusion of what RUN in a Dockerfile does. It > executes the command during the build of the image. That would be > handled by a shell provisioner in Packer. > > What process gets started when you /run/ the container from the > resulting image is handled by ENTRYPOINT and CMD those can be set in > packer with the changes 1). > > 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. > > 1) https://packer.io/docs/builders/docker.html#changes
Thanks for the clarification between running a container and building it, this was needed indeed (I realized my explanation might not have been clear enough on this front). 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/d76729ed-847b-199f-845b-d9dabca67426%40datameer.com. For more options, visit https://groups.google.com/d/optout.
