Failed to open TCP connection to stager.service.cf.internal:8888

[IvanAR]

When trying to push a docker app to CF, i'm getting the folowing error:

Server error, status code: 500, error code: 170011, message: Stager error: Failed to open TCP connection to stager.service.cf.internal:8888 (getaddrinfo: Name or service not known)

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/129534861

The labels on this github issue will be updated when the story is started.

[emalm]

Thanks for the report, @IvanAR. What versions of the CF and Diego BOSH releases are you running, and on what infrastructure?

That error message indicates that the Cloud Controller is unable to look up the stager component on the CC-Bridge via stager.service.cf.internal in Consul DNS. Does it occur only for Docker-image based apps, or also for buildpack-based apps? If you have any existing apps running, are you able to run cf apps or cf app APP_NAME successfully, or do you get a similar error?

Also, could you please run bosh instances --ps against your CF and Diego deployments and share the output? It would be helpful to verify that the consul_agent job is co-located with both the Cloud Controller and the CC-Bridge jobs and that everything is reporting as running.

Thanks,
Eric, CF Runtime Diego PM

[IvanAR]

Hi @ematpl,

I'm running a BOSH Lite inside Virtual Box with CF version 6.21.1+6fd3c9f-2016-08-10
For the releases, I used the tarball in this link http://bosh.io/releases/github.com/cloudfoundry/cf-release

I tried only with docker, no buildpack-based.

When i run cf apps, it returns me the deployed app (and no errors):

name      requested state   instances   memory   disk   urls
midgard   stopped           ?/1         256M     1G     midgard.bosh-lite.com

I think something strange hapenned with command bosh instances --ps:

vagrant@agent-id-bosh-0:~$ bosh instances --ps
RSA 1024 bit CA certificates are loaded due to old openssl compatibility
Please choose deployment first

If i run bosh vms, i get:

vagrant@agent-id-bosh-0:~$ bosh vms
RSA 1024 bit CA certificates are loaded due to old openssl compatibility
Acting as user 'admin' on 'Bosh Lite Director'
Deployment 'cf-warden'

Director task 39

Task 39 done

+---------------------------------------------------------------------------+---------+-----+-----------+--------------+
| VM                                                                        | State   | AZ  | VM Type   | IPs          |
+---------------------------------------------------------------------------+---------+-----+-----------+--------------+
| api_z1/0 (ce6cf8fc-ee3e-4bd9-9859-334d5dc39c5c)                           | running | n/a | large_z1  | 10.244.0.138 |
| blobstore_z1/0 (9a52cb43-5cc8-40df-bc31-20de6f59030c)                     | running | n/a | medium_z1 | 10.244.0.130 |
| consul_z1/0 (77550e2c-8f21-421a-a838-ade9fafc0f35)                        | running | n/a | small_z1  | 10.244.0.54  |
| doppler_z1/0 (333b62ef-9e7e-49c8-a501-fd1d947f6e00)                       | running | n/a | medium_z1 | 10.244.0.146 |
| etcd_z1/0 (cd2550ca-6a53-4a79-9bb5-24f84df07aa7)                          | running | n/a | medium_z1 | 10.244.0.42  |
| ha_proxy_z1/0 (7966058e-86e7-4fe7-9c9c-772776fa38b8)                      | running | n/a | router_z1 | 10.244.0.34  |
| hm9000_z1/0 (5c536380-4d97-4b39-8fe3-2f9e0556ef9f)                        | running | n/a | medium_z1 | 10.244.0.142 |
| loggregator_trafficcontroller_z1/0 (cbebf626-1877-4e7b-84dc-0919966abfb1) | running | n/a | small_z1  | 10.244.0.150 |
| nats_z1/0 (2661d4f1-e16e-45a8-a819-16e8c800048d)                          | running | n/a | medium_z1 | 10.244.0.6   |
| postgres_z1/0 (7433d519-12b7-41fd-abeb-cc3d2d51ff58)                      | running | n/a | medium_z1 | 10.244.0.30  |
| router_z1/0 (320c6019-5b34-4d8a-ac33-ab405ee21d9f)                        | running | n/a | router_z1 | 10.244.0.22  |
| runner_z1/0 (efdf8423-a1dd-49d4-9d2e-3c7cfd02a168)                        | running | n/a | runner_z1 | 10.244.0.26  |
| uaa_z1/0 (00d9db65-8a2d-49a3-9aa4-8b360a251d9d)                           | running | n/a | medium_z1 | 10.244.0.134 |
+---------------------------------------------------------------------------+---------+-----+-----------+--------------+

VMs total: 13

Thanks for the help!
Att,
Ivan A. Reffatti

[emalm]

Hi, @IvanAR,

From your bosh vms output, you don't seem to have Diego deployed. With the current manifest-generation templates in cf-release, it's still a separate deployment from the CF deployment, but you can find instructions at https://github.com/cloudfoundry/diego-release/tree/develop/examples/bosh-lite. If you're interested in running Docker images as CF apps, you'll also have to make sure to enable the Docker feature flag via cf enable-feature-flag diego_docker. Please let us know if you have questions!

Thanks,
Eric

[IvanAR]

Hi @ematpl ,

Thanks for the help, now it's working! But I'm worried about this point in the documentation:

• Diego does not currently support fetching images from private repositories.

Is private repositories going to be supported? If yes, do you have a deadline?

Thanks,
Ivan

[emalm]

Hi, @IvanAR,

We intend CF at some point to support fetching images from Docker registries or repositories that require authentication, but there aren't yet stories in the appropriate team trackers, so no clear estimate on when it will be implemented.

Thanks,
Eric

[emalm]

Also, since your original issue is resolved, I'll close out this issue.

Best,
Eric

[IvanAR]

Yes, thank you very much!