Thanks for following up. I recently found a mention of TMPDIR issue and deployed the latest diego with v0.330.0. Appears to have resolved the issue. Tom

cf 225, diego 0.1446.0, etcd 22, garden-linux 0.330.0 Deployed fine. Log in with admin, no problems. cf create-user -- works, user can login cf set-org-role or cf set-space-role -- "Server error, stat

Thanks for the pointer. Now the problem: garden.stdout.log: {"timestamp":"1453002747.400245667","source":"garden-linux","message":"garden-linux.pool.acquire.provide-rootfs- failed","log_level":2,"data

CF: 225 Diego: 0.1441.0 Default to diego. I deploy a sample app, no problems. I attempt to deploy another app that fails, because of application issues. A deploy of any other app fails with: 2016-01-1

A 0.1441.0 install without the docker cache, pulled from a private registry, no auth, no problems. I'm confused by this thread.

Hi, I wish to confirm, diego(v0.1441.0) only pulls from v2 registry now and not backward compatible with v1? What diego version switched out versions? Thanks, Tom

Hi Eric, Thank you. These questions sent me in the right direction. On the CC VM: To be clear, this vm is labeled api_z1, where I got the log from, and running cloud_controller_ng. No consul was runni

Hi Eric, Thanks for the pointers. `bosh vms` -- all running Only 1 api vm running. cloud_controller_ng.log is almost constantly being updated. Below is the 500 error capture: {"timestamp":1449752019.6

I'm giving CF 225 and diego 0.1441.0 a run. CF 225 is up and app deployed. Stop app. cf enable-diego app. Start app: FAILED Server error, status code: 500, error code: 10001, message: An unknown error

Hi Eric, Thank you. I am responding below with what I have available. Unfortunately, when the problem presents, developers are down so the current resolution is recreate cells. Looking at one below 98

diego release 0.1398.0 After a couple of weeks of dev, the cells end up filling their disks. Did I miss a clean up job somewhere? Currently, once pushes start failing, I get bosh to recreate the machi

Is there an equivalent of xray or ltc visualize for diego enable CF environment? Thanks, Tom

Hi, I'm getting into the services aspects of cloud foundry. I've deployed cf-redis-release. I've got 5 service instances, when I try to create another: Server error, status code: 502, error code: 1000

Lesson: take error messages literally Cell had a filled disk partition. Yes, insufficient resources. Changed machine type, and all good. Tom

After upgrade to/deploy diego in multiple environments with success, I'm a bit stumped on error for a new install. A cf docker-push results in: 015-09-26T16:02:01.65+0000 [API/0] OUT Updated app with

Thank you. The pointer to the code is excellent. I was looking in the right place. An odd part was I actually added the CA to the machine itself and it still did not work. I finally opted for a mirror

What is the default memory size of an app deployed in diego? cf apps indicate 1GB. cf set-env doesn't appear to be getting the environment variable information to the running container. Is cf set-env

Successfully deployed from a registry with a public cert. A registry with a private/self-signed cert fails at the stager. I've got the name of the registry in insecure_docker_registry_list and insecur

Yes! Thank you. Now on to registry debugging. The command did enable it. Tom

Deployed via http://www.evoila.de/cloud-foundry/adding-diego-release-to-cloud-foundry-release-v212/?lang=en (with v214 and 1398).(thanks for the write up) All deployed. Sample go app, pushed and diego