Background Process is not running on the VM created using packer image

18 views
Skip to first unread message

Rohit Juyal

unread,
Jan 2, 2019, 1:19:44 AM1/2/19
to Packer
Hello, I am creating an image using packer based on Ubuntu 16.04 OS. While creating the image I have executed this command in the script file to start a background process.

        command: "nohup gunicorn -b 0.0.0.0:7600 -w 1 -t 300 ae_app:app > updte.log 2>&1 &"

ae_app is an app created in python. While creating the image I can see the script running and process also started and then the image created. But when I create a VM using this image, the process is not running in the background.

Rickard von Essen

unread,
Jan 2, 2019, 4:41:23 AM1/2/19
to packe...@googlegroups.com
AMI are essentially a disk image used to initiate the disk when creating a new instance. Of course processes don't survive reboots. It's probably good to pick up a book about Linux and specifically read up about systemd service units and systemd in general. 

--
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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/04c30bca-ec15-4ebd-910e-45a4d5542c63%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply all
Reply to author
Forward
0 new messages