# Kitchen create: "Waiting for SSH service on localhost"
**URL:** https://discourse.chef.io/t/kitchen-create-waiting-for-ssh-service-on-localhost/10967
**Category:** Chef Infra (archive)
**Created:** [May 30, 2017, 3:05pm UTC](https://discourse.chef.io/t/kitchen-create-waiting-for-ssh-service-on-localhost/10967 "2017-05-30T15:05:25Z")
**Posts on this page:** 1
**Page:** 1
### Author:  [@jon.ljh](https://discourse.chef.io/u/jon.ljh)
#### Post date: [May 30, 2017, 3:05pm UTC](https://discourse.chef.io/t/kitchen-create-waiting-for-ssh-service-on-localhost/10967/1 "2017-05-30T15:05:26Z")
Hello:
When I do a **kitchen create default-ubuntu-1404** , it appears to run through a series of steps but hangs on the following error message:
Waiting for SSH service on localhost:32770, retrying in 3 seconds
Waiting for SSH service on localhost:32770, retrying in 3 seconds
Waiting for SSH service on localhost:32770, retrying in 3 seconds
Waiting for SSH service on localhost:32770, retrying in 3 seconds
Waiting for SSH service on localhost:32770, retrying in 3 seconds
Waiting for SSH service on localhost:32770, retrying in 3 seconds
My .kitchen.yml file is very simple:
driver:
name: docker
```
provisioner:
name: chef_zero
platforms:
- name: ubuntu-14.04
suites:
- name: default
run_list:
- recipe[nginx::default]
```
I'm running the test/create on a aws ec2 with docker installed locally.
Any thoughts?
I've looked at a series of posts, but I'm having a hard time applying the fixes, or understanding what the root cause of the issue is. Here are some related posts:
> [@Kitchen-EC2 Waiting for SSH Service" loop Error(Ubuntu Image)!](https://discourse.chef.io/t/kitchen-ec2-waiting-for-ssh-service-loop-error-ubuntu-image/9003/5):
>
> Manual SSH is nothing related with config. i just put this to manual ssh, ssh -i "sysadmin.pem" ubuntu@10.10.70.176 Here’s my kitchen.yml file here. Please chef if anything is wrong in it, --- driver: name: ec2 aws\_ssh\_key\_id: sysadmin region: ap-south-1 instance\_type: t2.micro security\_group\_ids: ["sg-xxxxx"] subnet\_id: subnet-xxxxx require\_chef\_omnibus: true transport: ssh\_key: .ssh/sysadmin.pem provisioner: name: chef\_zero platforms: - name: ubuntu-16.04 ima…
> [@Test kitchen using vagrant - ssh issue](https://discourse.chef.io/t/test-kitchen-using-vagrant-ssh-issue/9979/6):
>
> Using HP laptop? I had an issue using Vagrant with VirtualBox on HP machine. The root cause of the issue was that the PC system not enabled with VTx technology. To enable VTx option on HP laptop: Reboot the system and then hit “Esc” key Jump into “device configuration” to set device bios options Select “Advanced” tab Check the option on “Vitualization Technology(VTx)”, save it and exit Reboot the system
> [@Kitchen test using vagrant/virtualbox](https://discourse.chef.io/t/kitchen-test-using-vagrant-virtualbox/6788):
>
> Hello, I am running into some issues trying to boot a 64 bit CentOS/RHEL instance from VirtualBox, installed on a RHEL VM using ESXi for virtualization. It works fine with 32 bits VMs, but as I understand, for 64 bits, I need to enable VT-x/AMD-V in the BIOS setting of the Physical Server CPU to be able to run 64-bit operating systems inside of them. I am not sure if this would work running on virtualization and/or nested VMs. Output: Bringing machine ‘default’ up with ‘virtualbox’ provider… …
>
>
> After successfully building the image and starting a container, I am seeing this… output from kitchen:
>
> \`\`\`
> Successfully built 5901cc403a60
> 6ceee57d6513d02b4ffc5816b3f3a0167e423a3375691046279e414c27acef4e
> 0.0.0.0:32775
> Waiting for SSH service on localhost:32775, retrying in 3 seconds
> Waiting for SSH service on localhost:32775, retrying in 3 seconds
> Waiting for SSH service on localhost:32775, retrying in 3 seconds
> Waiting for SSH service on localhost:32775, retrying in 3 seconds
> Waiting for SSH service on localhost:32775, retrying in 3 seconds
> Waiting for SSH service on localhost:32775, retrying in 3 seconds
> Waiting for SSH service on localhost:32775, retrying in 3 seconds
> \`\`\`
>
> I know that the port is accessible, in part because of \`docker ps\` output but also because I can telnet to the port:
>
> \`\`\`
> ~$ docker ps
> CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
> 6ceee57d6513 5901cc403a60 "/sbin/init" 11 minutes ago Up 11 minutes 0.0.0.0:32775-\>22/tcp defaultcentos6-oswaltm-C02RF1RYFVH8-mjgnwpli
> d37cddf0039f 5901cc403a60 "/sbin/init" 12 minutes ago Up 12 minutes 0.0.0.0:32774-\>22/tcp defaultcentos7-oswaltm-C02RF1RYFVH8-wau9mycw
>
> ~$ telnet localhost 32775
> Trying ::1...
> Connected to localhost.
> Escape character is '^\]'.
> SSH-2.0-OpenSSH\_6.6.1
> \`\`\`
>
> So, I suspect it could be an auth issue perhaps, but am not sure how kitchen tries to auth to the container. Any ideas?