Thanks for the reply. I just attached my current files.
On Friday, September 16, 2016 at 10:24:44 AM UTC-7, Rjaydee wrote:
>
> I am trying to deploy and set a vm using packer and a kickstart file. This
> packer code:
>
> {
> "builders": [
> {
&g
n the VM, you can access the outside world and check if you
>> get any messages in the logs about auth fail etc.
>>
>>
>> On Friday, September 16, 2016 at 7:24:44 PM UTC+2, Rjaydee wrote:
>>>
>>> I am trying to deploy and set a vm using packer and a kickstar
sole access
> (VMRC/vSphere/ESXi Embedded Host Client) login there and check if the
> network is up in the VM, you can access the outside world and check if you
> get any messages in the logs about auth fail etc.
>
> On Friday, September 16, 2016 at 7:24:44 PM UTC+2, Rjaydee wrote:
>&
Pleae find attached my modified files
>
--
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.
st enable root ssh login in /etc/ssh/sshd_config
> by setting PermitRootLogin yes
> The simplest way to do this is probably adding this to your ks.cfg before
> %end
>
> %post
> sed -i 's/.*PermitRootLogin .*/PermitRootLogin yes/' /etc/ssh/sshd_config
>
>
> On
gt;
> %post
> sed -i 's/.*PermitRootLogin .*/PermitRootLogin yes/' /etc/ssh/sshd_config
>
>
> On 17 September 2016 at 01:49, Rjaydee >
> wrote:
>
>> Hello Richard, I am sorry if this question seems dumb, but I just started
>> learning/uisng a packer a
e.json and
>> gist the output and link here. Or if you have a console access
>> (VMRC/vSphere/ESXi Embedded Host Client) login there and check if the
>> network is up in the VM, you can access the outside world and check if you
>> get any messages in the logs about auth
ne. How would you do it? Just started doing
this a few days ago, so I am still learning.
On Friday, September 16, 2016 at 11:50:04 PM UTC-7, Rickard von Essen wrote:
>
> Ok then you need to get a console and login and troubleshoot your network.
> Most likely your network is not properly s
; Fusion/Workstation or VirtualBox which is much more straight forward and
> you can revisit building on ESXi when you got a hang on it. ESXi/vSphere is
> a very complex product and there lots of thing that can go wrong outside of
> Packers control.
>
> On Saturday, September 17, 20
Good advice. I will go back and master the foundation first. Thanks.
On Saturday, September 17, 2016 at 4:59:13 AM UTC-7, Alvaro Miranda
Aguilera wrote:
>
> Hello,
>
> I will suggest slow down a bit.
>
> You should automate something that you know it words and ideally you have
> done it properl
After doing reseach, and tests. The error seems to be at this part of the
ks.cfg file.
#Network Information
network --bootproto=static --device=eno16780032 --gateway=8.1.140.1
--ip=8.1.142.187 --nameserver=8.1.44.254,8.1.32.254 --netmask=255.255.252.0
--noipv6 --activate --hostname=myhost.com
Can you please help me understand why this is happening? I have been trying
for a while now, and I am still getting the same results
On Friday, September 16, 2016 at 10:24:44 AM UTC-7, Rjaydee wrote:
>
> I am trying to deploy and set a vm using packer and a kickstart file. This
> pa
12 matches
Mail list logo
