I’ve created custom Windows_10_PRO_1909_x64 image with hashicorp packer (with QEMU). To build it I used unattend.xml file. Steps to prepare were: Absolutely unattended installation of Windows Installation of big amount of software Converting VM (it was build with QEMU) to raw .img file Now I want to deploy this image to new PC. I’m using ..
i’m working with packer to create virtual machine windows on virtualbox that it work with WINRM but always bug in waiting winrm to become available what is the problem the version of packer bug in winrm ? or it’s normally that it take a long time ? or there is something i should add in ..
I am trying to create a windows server 2016 base AMI using packer. But in order for packer to get into the instance, we need to bootstrap and enable winrm first. Referring this for the bootstrap_win script file: https://learn.hashicorp.com/tutorials/packer/aws-windows-image However, timeout happens waiting for winrm (tried setting winrm_timeout too, but it takes more time and ..
Has anyone come across this problem and why it happens? Im trying to set up my winrm listeners on a custom image so I can ansible back into that machine. Has anyone got any solutions? The sysprep is through ec2 launch powershell scripts Source: Windows..
I am in the process of creating a Packer file to create a Windows 2019 standard edition server template. The initial step works without any obvious errors and creates a template. However. when creating a new server from the template. I get the following behaviour. Open up a web console and the ctrl-alt-insert keys do ..
I get the error "awsAccessKey value is null" when trying to access S3 or SSM from an AMI provisioned by Packer. I am using an inline Powershell provisionner. The inline code calls a ps1 file in which I attempt to download from S3 or access SSM. The IAM role on the EC2 has correct permissions. ..
I’m taking the Udacity course to learn more in the field of DevOps (https://github.com/udacity/devops-intro-project), but if I use the following line in the Windows command prompt: packer build -only=virtualbox-iso application-server.json I get the following error message: C:UserskelvinDownloadsDocumentsDevOpspacker-templates>packer build -only=virtualbox-iso application-server.json Error: Failed to prepare build: "virtualbox-iso" 1 error occurred: * Deprecated configuration key: ‘iso_checksum_type’. Please ..
The question has probably been asked before, but I couldn’t find a reference. I am using packer to build custom Windows AWS AMI. After the packer build, I provisioned an EC2 instance using the AMI and noticed WinRM service is running and the Firewall rule I had set in user_data is also enabled. I don’t ..
I’m running packer outside of azure and I can’t use public ips for vms. Using the ssh communicator for creating linux vm images I’m able to use the bastion host configurations. I’m unable to figure out how to accomplish this with windows via winrm though. Any ideas? Source: Windows..
I am able to harden the Windows 2019 Standard Image using packer using LGPO.exe However, immediately after hardening it, the packer fails to connect to the EC2, I presume its due to CIS hardening itself. I have googled everywhere, but could not find a get around. below is the error message packer-builder-amazon-ebs plugin: Uploading file ..