[packer] Packer and Chef-Solo Provisioner

I am using packer to make AMIs. I have placed most of my code within Chef and I using the Chef-Solo provisioner to call the required cookbooks. I have configured a reboot within my cookbook for certain software installs. Whenever the reboot happens during the packer build process it will

[packer] Re: packer ansible provisioner host_vars groups_vars

Thanks for answer. But you have had success in using host_vars and group_vars in ansible provisioner at packer script? пятница, 6 апреля 2018 г., 0:16:28 UTC+3 пользователь Matthieu написал: > > Hi Tony, > > Unfortunately i do work for the company i was working for at the time of > those

[packer] Packer v1.2.1 - WinRM communicator timeout

Hey all, Am using the WinRM communicator with Packer 1.2.1 using the vmware-iso builder. I get the WinRM timeout unless I specify the IP address of the target VM using "winrm_host". My packer exe is on a different subnet to the target VM but there is routing in place, as demonstrated that it

Re: [packer] Docker Container Shouldn't Killed

Hello Packer won't run your docker container. Packer only build docker images. You need run it by hand, script or a different tool. Not sure from where you are getting the idea that packer can be used to run containers, thats what I have been trying to explain. Alvaro. -- This mailing list

Re: [packer] Docker Container Shouldn't Killed

Yes Sure, Once Docker Images is Build, After That i want to run Docker Images so that Container can up. Docker Images is Build { "builders": [ { "type": "docker", "image": "tomcat", "commit": "true",

Re: [packer] Docker Load Tar File

Hello Its always better to have packer clean, and you can use a shell script to wrap pre-requirements as packer usually check state before running, may/may not work in the way you want. There is a provisioner named shell-local you can use to run commands in the host but its too late to import a

Re: [packer] Docker Container Shouldn't Killed

Hello Can you explain more? Packer is to build docker images, not to run docker images. After packer is run, no containers should be running as part of this. On Fri, Apr 6, 2018 at 12:02 PM, Saurabh wrote: > Hi Alvaro, > > Thanks for your response. > > Tagging

[packer] Docker Load Tar File

Hi All, How I can use packer for docker load --input tomcat.tar command ? Any Solutions for this ? Regards Saurabh -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines

Re: [packer] Docker Container Shouldn't Killed

Hi Alvaro, Thanks for your response. Tagging Name it will not resolve my issue. I'm looking something - packer should generate the docker image - Ansible will do configuration on docker image - and finally Container should run without any manual interaction. Please help me for

Re: [packer] AMI Tags not propagated to other accounts?

This is how AWS works. AMI's can be shared with other accounts, basically giving them read access. But tags are a separate construct, metadata separate from the resources they "tag". They are not shared and and not visible from the other account just because the AMI is shared. The other account

Re: [packer] Docker Container Shouldn't Killed

Hello Packer build a container, and in your code will be commited if you check docker images the top one will be the new one you did. You can add a post-processor docker-tag to tag that container ie "post-processors": [ { "repository": "myxenial", "tag": "latest", "type": "docker-tag" }

[packer] Docker Container Shouldn't Killed

Hi All, While Running to Packer Build Command. at last Docker Container is getting Killed. I don't want docker Container should killed. It should run Container. * ==> docker: Killing the container: 4fca9b0df6764361fefee08e4053e073ecc869a5de72e76d885dfa4f2f6cda7a

[packer] AMI Tags not propagated to other accounts?

I have built an AWS AMI image using the EBS backed builder and I set the "ami_users" to a couple of different accounts so the ami is available for using in all of these acounts. I noticed that the AMI in the account which I built the image on has all the AMI tags I configured in the packer