[packer] Re: Windows Hardening and WinRM

2018-01-06 Thread Jordan Borean
I would say the SeNetworkLogonRight is causing the issue, SID S-1-0-0 is Nobody which means that no user will be able to access resources of the host through the network. This can include things like WinRM and file/print services. I would change that to be the WinRM user you are working with at

[packer] Windows Hardening and WinRM

2018-01-06 Thread Mathias Woringer
Hello everyone, I'm trying to build a Windows Server 2012 r2 virtualbox vm with some hardening using Chef-Solo. There was an issue using Chef-Solo and WinRM, but Packer version 1.1.4 solves the issue. I'm not a Windows expert and am using the hardening cookbooks from this project: https://g

Re: [packer] VirtualBox Guest Additions: modprobe vboxsf failed

2018-01-06 Thread Robert Wang
Thanks this is the easy way what I am looking for to by pass the unwanted exit code. -- 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 m

Re: [packer] VirtualBox Guest Additions: modprobe vboxsf failed

2018-01-06 Thread Rickard von Essen
Most likely this is because you are building against a newer kernel version that you just installed (with apt-get update etc) but is not yet running since you haven't rebooted. See how bento does it: https://github.com/chef/bento/blob/master/_common/virtualbox.sh https://github.com/chef/bento/blob

Re: [packer] why packer stop for any error?

2018-01-06 Thread Rickard von Essen
Since it's an automation tool it kind of defeats the purpose of it. And also it could lead to inconsistent state so Packer would crash later on. On 6 January 2018 at 14:12, Robert Wang wrote: > Thanks, I did try -on-error=ask, there are 3 options: > clean(default), abort (left vm), ask(retry) >

Re: [packer] why packer stop for any error?

2018-01-06 Thread Robert Wang
Thanks, I did try -on-error=ask, there are 3 options: clean(default), abort (left vm), ask(retry) sometimes I know the error is not critical and cannot avoid it for some reason, seems no way to ignore the error to continue build box? BR/ Robert On Saturday, January 6, 2018 at 2:32:09 AM UTC-

[packer] VirtualBox Guest Additions: modprobe vboxsf failed

2018-01-06 Thread Robert Wang
I am trying to build ubuntu dev box using packer, this virtualbox guest installation is one of script: ubuntu-vbguest.sh export DEBIAN_FRONTEND=noninteractive apt-get install -y -q gcc build-essential mount -o loop,ro VBoxGuestAdditions.iso /mnt yes | sudo sh /mnt/VBoxLinuxAdditions.run umoun