Looks like Docker can't get out to the Internet to fetch the CentOS image. Make 
sure the box you are on has Internet access or if is behind a proxy has the 
proxy variables set. 

> On May 23, 2016, at 04:26, Dibyendu Paul <[email protected]> wrote:
> 
> Hi Jason
> Any idea about this error?
> [root@controlserver vmware-rhel-server-builder]# /usr/bin/docker build -t hs .
> Sending build context to Docker daemon 1.032 MB
> Sending build context to Docker daemon
> Step 0 : FROM centos
> Pulling repository centos
> Get https://index.docker.io/v1/repositories/library/centos/images: dial tcp 
> 52.73.94.64:443: connection timed out
> [root@controlserver vmware-rhel-server-builder]#
> 
> 
> 
>> On Wednesday, 11 May 2016 16:25:01 UTC+5:30, Jason Hiatt wrote:
>> That looks correct, make sure CONTAINERHOSTNAME is changed to the hostname 
>> that is running your Docker container. 
>> 
>>> On May 10, 2016, at 23:04, Dibyendu Paul <[email protected]> wrote:
>>> 
>>> Thanks Jason.
>>> Just to make sure that I am doing it right.
>>> Could you please confirm if this is correct. I have changed the texts 
>>> marked in BOLD.
>>> 
>>> default ks
>>> #prompt 1
>>> timeout 600
>>> 
>>> display boot.msg
>>> 
>>> menu background splash.jpg
>>> menu title Welcome to Red Hat Enterprise Linux 6.5!
>>> menu color border 0 #ffffffff #00000000
>>> menu color sel 7 #ffffffff #ff000000
>>> menu color title 0 #ffffffff #00000000
>>> menu color tabmsg 0 #ffffffff #00000000
>>> menu color unsel 0 #ffffffff #00000000
>>> menu color hotsel 0 #ff000000 #ffffffff
>>> menu color hotkey 7 #ffffffff #ff000000
>>> menu color scrollbar 0 #ffffffff #00000000
>>> 
>>> label linux
>>>   menu label ^Install or upgrade an existing system
>>>   menu default
>>>   kernel vmlinuz
>>>   append initrd=initrd.img
>>> label vesa
>>>   menu label Install system with ^basic video driver
>>>   kernel vmlinuz
>>>   append initrd=initrd.img xdriver=vesa nomodeset
>>> label rescue
>>>   menu label ^Rescue installed system
>>>   kernel vmlinuz
>>>   append initrd=initrd.img rescue
>>> label local
>>>   menu label Boot from ^local drive
>>>   localboot 0xffff
>>> label memtest86
>>>   menu label ^Memory test
>>>   kernel memtest
>>>   append -
>>> label ks
>>>   menu label ^Kickstart installation
>>>   kernel kickstart
>>>   append kssendmac ks.sendmac inst.ks.sendmac 
>>> ks=http://CONTAINERHOSTNAME/kickstart/ks.php?osid=rhel7_64Guest
>>> 
>>> 
>>> 
>>> 
>>> 
>>>> On Wednesday, 11 May 2016 03:31:58 UTC+5:30, Jason Hiatt wrote:
>>>> Yes, the isolinux.cfg file, this link may explain better. 
>>>> http://vuksan.com/linux/kickstart_boot_cd.html
>>>> 
>>>>> On May 10, 2016, at 05:30, Dibyendu Paul <[email protected]> wrote:
>>>>> 
>>>>> Thanks Great Jason.
>>>>> But I have a silly question.
>>>>> where exactly (Which file) do I insert the following line: kssendmac 
>>>>> ks.sendmac inst.ks.sendmac 
>>>>> ks=http://CONTAINERHOSTNAME/kickstart/ks.php?osid=rhel6_64Guest
>>>>> The link you mentioned ( 
>>>>> http://serverfault.com/questions/517908/how-to-create-a-custom-iso-image-in-centos)
>>>>>  basically used the kickstart file and here I suppose the boot line needs 
>>>>> to be added. where do I put the boot line in that case? Is it the 
>>>>> isolinux.cfg file I need to modify?
>>>>> 
>>>>> 
>>>>>> On Tuesday, 10 May 2016 07:17:56 UTC+5:30, Jason Hiatt wrote:
>>>>>> Instructions are finally up, sorry it took so long, ran into some bugs 
>>>>>> while I was Dockerizing the app. Please try it out and let me know what 
>>>>>> problems you come across. 
>>>>>> 
>>>>>> 
>>>>>>> On May 5, 2016, at 21:44, Dibyendu Paul <[email protected]> wrote:
>>>>>>> 
>>>>>>> Hi Jason
>>>>>>> Is there any instructions available yet?
>>>>>>> 
>>>>>>>> On Friday, 29 April 2016 18:12:20 UTC+5:30, Jason Hiatt wrote:
>>>>>>>> Yes, I am going to update code and write up some instructions this 
>>>>>>>> weekend.  I have a big project at work I need to finish up before I 
>>>>>>>> can get to that though.
>>>>>>>> 
>>>>>>>> If you want to make multiple VMs I would write a script that calls the 
>>>>>>>> createVM.php web service.
>>>>>>>> 
>>>>>>>> All you would  have to do is call curl, for example.  curl 
>>>>>>>> "http://test.example.com/ws/createVM.php?vmname=${VMName}&ipaddress=${IPAddress}&cpus=2.......";
>>>>>>>> 
>>>>>>>> Thanks,
>>>>>>>> Jason
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>>> On Thu, Apr 28, 2016 at 1:44 AM, Dibyendu Paul 
>>>>>>>>> <[email protected]> wrote:
>>>>>>>>> Also The current Web UI allows to create one  VM at a time. Is It 
>>>>>>>>> possible to create Multiple VMs at a time?
>>>>>>>>> 
>>>>>>>>>  
>>>>>>>>> 
>>>>>>>>>> On Wednesday, 27 April 2016 04:19:26 UTC+5:30, Jason Hiatt wrote:
>>>>>>>>>> 
>>>>>>>>>> Yes, you could specify the installation server in your custom ISO.
>>>>>>>>>> I think the correct option to use is "inst.repo="
>>>>>>>>>> 
>>>>>>>>>> We just use the installation source from the DVD.
>>>>>>>>>> 
>>>>>>>>>> Thanks,
>>>>>>>>>> Jason
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>>> On Sun, Apr 24, 2016 at 11:32 PM, Dibyendu Paul 
>>>>>>>>>>> <[email protected]> wrote:
>>>>>>>>>>> Hi Jason
>>>>>>>>>>> This is excellent!
>>>>>>>>>>> In this setup is it possible to pick the RHEL OS from the 
>>>>>>>>>>> Installation server? where the iso could be kept or local 
>>>>>>>>>>> repository could be created?
>>>>>>>>>>> 
>>>>>>>>>>> Regards
>>>>>>>>>>> Dibyendu Paul
>>>>>>>>>>> 
>>>>>>>>>>>> On Monday, 25 April 2016 08:37:30 UTC+5:30, Jason Hiatt wrote:
>>>>>>>>>>>> We have a web UI that lets our admins input IP, VM name, number of 
>>>>>>>>>>>> CPUs, RAM and other attributes.
>>>>>>>>>>>> You can see a stripped down version of it here -> 
>>>>>>>>>>>> https://github.com/OneMainF/vmware-rhel-server-builder/blob/master/build/src/www/createVM.html
>>>>>>>>>>>> 
>>>>>>>>>>>> The web UI calls this web service when all inputs are entered -> 
>>>>>>>>>>>> https://github.com/OneMainF/vmware-rhel-server-builder/blob/master/build/src/www/ws/createvm.php
>>>>>>>>>>>> 
>>>>>>>>>>>> The web service adds the server to a database and creates an 
>>>>>>>>>>>> Ansible play and runs it.  The playbook creates the VM and 
>>>>>>>>>>>> collects the VM's MAC address and updates the DB.
>>>>>>>>>>>> 
>>>>>>>>>>>> Once the VM starts up the dynamic Kickstart file is called and the 
>>>>>>>>>>>> VM is built.
>>>>>>>>>>>> https://github.com/OneMainF/vmware-rhel-server-builder/blob/master/build/src/www/kickstart/ks.php
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> I'm getting closer to Dockeizing the application, hopefully I can 
>>>>>>>>>>>> get it done this week.
>>>>>>>>>>>> 
>>>>>>>>>>>>> On Thu, Apr 21, 2016 at 11:24 PM, Dibyendu Paul 
>>>>>>>>>>>>> <[email protected]> wrote:
>>>>>>>>>>>>> Hi
>>>>>>>>>>>>> How the kick start will pick individual ips of the vms. Where 
>>>>>>>>>>>>> those ips to be defined?
>>>>>>>>>>>>> The kick start will not have the up conf? How do you make it 
>>>>>>>>>>>>> generalized?
>>>>>>>>>>>>> 
>>>>>>>>>>>>> --
>>>>>>>>>>>>> You received this message because you are subscribed to a topic 
>>>>>>>>>>>>> in the Google Groups "Ansible Project" group.
>>>>>>>>>>>>> To unsubscribe from this topic, visit 
>>>>>>>>>>>>> https://groups.google.com/d/topic/ansible-project/Holm0CFBbLo/unsubscribe.
>>>>>>>>>>>>> To unsubscribe from this group and all its topics, send an email 
>>>>>>>>>>>>> to [email protected].
>>>>>>>>>>>>> To post to this group, send email to [email protected].
>>>>>>>>>>>>> To view this discussion on the web visit 
>>>>>>>>>>>>> https://groups.google.com/d/msgid/ansible-project/621f9dca-6d54-4e51-82ad-761be5a374bd%40googlegroups.com.
>>>>>>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>>>> 
>>>>>>>>>>> -- 
>>>>>>>>>>> You received this message because you are subscribed to a topic in 
>>>>>>>>>>> the Google Groups "Ansible Project" group.
>>>>>>>>>>> To unsubscribe from this topic, visit 
>>>>>>>>>>> https://groups.google.com/d/topic/ansible-project/Holm0CFBbLo/unsubscribe.
>>>>>>>>>>> To unsubscribe from this group and all its topics, send an email to 
>>>>>>>>>>> [email protected].
>>>>>>>>>>> To post to this group, send email to [email protected].
>>>>>>>>>>> To view this discussion on the web visit 
>>>>>>>>>>> https://groups.google.com/d/msgid/ansible-project/43674172-ecab-4a82-9450-11be01e5833b%40googlegroups.com.
>>>>>>>>>>> 
>>>>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>>> 
>>>>>>>>> -- 
>>>>>>>>> You received this message because you are subscribed to a topic in 
>>>>>>>>> the Google Groups "Ansible Project" group.
>>>>>>>>> To unsubscribe from this topic, visit 
>>>>>>>>> https://groups.google.com/d/topic/ansible-project/Holm0CFBbLo/unsubscribe.
>>>>>>>>> To unsubscribe from this group and all its topics, send an email to 
>>>>>>>>> [email protected].
>>>>>>>>> To post to this group, send email to [email protected].
>>>>>>>>> To view this discussion on the web visit 
>>>>>>>>> https://groups.google.com/d/msgid/ansible-project/ea0de6a9-eb1d-4a4a-aac0-d353fbaf7504%40googlegroups.com.
>>>>>>>>> 
>>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>> 
>>>>>>> -- 
>>>>>>> You received this message because you are subscribed to a topic in the 
>>>>>>> Google Groups "Ansible Project" group.
>>>>>>> To unsubscribe from this topic, visit 
>>>>>>> https://groups.google.com/d/topic/ansible-project/Holm0CFBbLo/unsubscribe.
>>>>>>> To unsubscribe from this group and all its topics, send an email to 
>>>>>>> [email protected].
>>>>>>> To post to this group, send email to [email protected].
>>>>>>> To view this discussion on the web visit 
>>>>>>> https://groups.google.com/d/msgid/ansible-project/5e3a18d9-237c-4f94-8f35-d1bd8d257a93%40googlegroups.com.
>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>> 
>>>>> -- 
>>>>> You received this message because you are subscribed to a topic in the 
>>>>> Google Groups "Ansible Project" group.
>>>>> To unsubscribe from this topic, visit 
>>>>> https://groups.google.com/d/topic/ansible-project/Holm0CFBbLo/unsubscribe.
>>>>> To unsubscribe from this group and all its topics, send an email to 
>>>>> [email protected].
>>>>> To post to this group, send email to [email protected].
>>>>> To view this discussion on the web visit 
>>>>> https://groups.google.com/d/msgid/ansible-project/82c774fd-3e0d-4bec-a815-5e4f2d6bed8b%40googlegroups.com.
>>>>> For more options, visit https://groups.google.com/d/optout.
>>> 
>>> -- 
>>> You received this message because you are subscribed to a topic in the 
>>> Google Groups "Ansible Project" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/ansible-project/Holm0CFBbLo/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to 
>>> [email protected].
>>> To post to this group, send email to [email protected].
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/ansible-project/8d29e924-a709-4a06-9b2a-96795cc646c6%40googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "Ansible Project" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/ansible-project/Holm0CFBbLo/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> [email protected].
> To post to this group, send email to [email protected].
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/ansible-project/4e29e978-87e7-4282-978a-b264423d977f%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/4380FF22-9C11-4A8C-8EAE-A1041B8C69D0%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to