How to push a app use the docker Backend in diego?

hello i have deploy the diego and cf, and i want to push a app, which can use the docker image created by myself. can you tell me how to do? thank you .

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: https://www.pivotaltracker.com/story/show/89336704.

[hsiliev]

Currently this is manually done with cf curl until CLI support is available.

You can have a look at how this is done in the acceptance tests:
https://github.com/cloudfoundry-incubator/diego-acceptance-tests/blob/master/diego/lifecycle_docker_test.go#L41

In general you want to do:

cf space <your space> --guid
cf curl  /v2/apps -X POST -d '{"name": "app", "memory": 512, "instances": 1, "disk_quota": 1024, "space_guid": "guid", "docker_image": "cloudfoundry/diego-docker-app:latest", "command": "/myapp/dockerapp", "diego": true }
cf start <name>

You will most probably want to add routes as well, so have a look at DATS here:
https://github.com/cloudfoundry-incubator/diego-acceptance-tests/blob/master/diego/lifecycle_docker_test.go#L42

[onsi]

Hi @hellolin

We actually have lots of details around Diego here:
https://github.com/cloudfoundry-incubator/diego-design-notes/blob/master/migrating-to-diego.md

In particular, the diego-beta CLI plugin includes support to cf docker-push :)

[tsjsdbd]

Hi @hsiliev

is this repoURL public? "docker_image": "cloudfoundry/diego-docker-app:latest"

what if i want use a private Docker image, which means need username and passwords. how can i deploy such a private image to CF?

Thanks

[georgethebeatle]

Hi @hellolin,

Yes, cloudfoundry/diego-docker-app:latest is a public image. Unfortunately currently it is not possible to push a private docker image. Me and @hsiliev are working on integrating a private registry with cf, so that you can - glad to hear that someone actually needs that 😄.

If you really need to keep your image private you can do the following:

• Spin up your own private docker registry (see https://github.com/cloudfoundry-community/docker-registry-boshrelease)
• Push your private image there
• Do a cf docker-push from the private registry.

Your image will be publically available in a private registry that is visible only from your network. Note that you will have to enable https in the private registry or cf won't trust it.

[tsjsdbd]

Hi @georgethebeatle @hsiliev

thanks for reply, but your describe is not match what I want exactly. the registry maybe public, but the repository is private which belong to that public registry, like Docker Hub.
Think about this scenario: if we have a Docker registry along with CF, and each CF user has his own repository, he can login this Docker repository use CF username&passwords with docker CLI, and he want to deploy his private docker image from his own repository by CF. So how CC pass the Token to garden?(diego doesn't hold user information, only CC have it)

I see this code before fetch Docker Image, it get Token from RepoURL, but the "docker_image" url can not be user:pass@docker-images-local.mydomain.com:443/bar, right?

how can i deploy such a private image to CF? if I have to modify the cf code, what kind of method is smooth?

Thanks

[nagarakesh4]

Hello @georgethebeatle,

Is still pushing private docker registry images to CF not in place? The api at http://apidocs.cloudfoundry.org/213/apps/creating_a_docker_app_(experimental).html, doesn't mention anywhere about pushing to cf from a private docker repo.

[hsiliev]

Hi @nagarakesh4,

The support for private images from Docker Hub is working and tested with the latest versions of Diego & CF. The documentation does not look well and I created a bug to fix this. In general yours docker_credentials_json section should resemble this:

...
    "docker_credentials_json" : {
        "docker_user" : "user name",
        "docker_password" : "password",
        "docker_email" : "email"
    },
...

You can currently push an image with cf curl /v2/apps -X POST -d <payload> with payload like the one we use in this test. You then need to execute cf set-env <application_name> DIEGO_DOCKER_CACHE true and start your app.

Be aware that your private registry has to use trusted certificate. The support for insecure (HTTP and self-signed HTTPS cert) is coming with the next story in our docker backlog.

[cxhercules]

Did anything get updated to improve documentation?