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 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

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] 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