-
Notifications
You must be signed in to change notification settings - Fork 943
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
app manifest should support referencing a docker image with docker registry #696
Comments
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/108983470. |
Hi @jbayer, Correct. We are focusing on exposing back-end features such as the routing related ones and manifest support is falling behind. It hasn't fallen off my radar though! Regards, |
@SocalNick The docker upload API is still marked |
i'm not aware of reasons it should still marked experimental. are there any? /cc @dieucao |
Maybe because FWIW, we intend to remove |
Hi @SocalNick and @dkoper My question is can we push docker image via manifest? ( docker_image: ) |
@jbayer Definitely! |
@dkoper Great to hear that Docker support is now planned for manifests. Is there an ETA when we can expect this feature? |
👍 |
@wmnnd, @motevets Are you planning to use only public Docker images, or also from private Docker repositories? The story for Docker image support in manifests is currently scheduled for delivery in 1-2 months. The ETA for the former is based on the current refactor of If demand is high enough, we can at least investigate how much effort and risk is involved in implementing it in the current |
@dkoper I am using only private registries. For now, I am using {
"name": "myapp",
"memory": 128,
"space_guid": "…",
"docker_image": "my.registry/image",
"docker_credentials": {
"username": "foo",
"password": "bar"
},
"environment_json": {
"FOO": "bar"
},
"diego": true
}
If I may make a suggestion about avoiding putting the credentials for private registries in the manifest: You already have |
My use case at the time was for a public image, but I would find private
images useful in the future.
I like solution @wmnnd proposed using environment variables. I'm also not
scared of putting credentials in my manifest because I already put
sensitive environment variables in my manifest, but don't check it in with
the source code.
…On Thu, Jul 13, 2017, 3:33 AM Philipp ***@***.***> wrote:
@dkoper <https://github.com/dkoper> I am using only private registries.
For now, I am using cf curl /v2/apps with a JSON file that looks
something like a manifest already and then a shell script to attach the
necessary services and routes:
{
"name": "myapp",
"memory": 128,
"space_guid": "…",
"docker_image": "my.registry/image",
"docker_credentials": {
"username": "foo",
"password": "bar"
},
"environment_json": {
"FOO": "bar"
},
"diego": true
}
If I may make a suggestion about avoiding putting the credentials for
private registries in the manifest: You already have CF_DOCKER_PASSWORD,
so if you added CF_DOCKER_USER, I think all would be good 😄
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#696 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAveLYoElgsuYFVicRtY63Aybatg6oVMks5sNfKBgaJpZM4GpiLu>
.
|
This feature is now supported in cf CLI 6.31.0 onwards. |
i didn't see support for it here and assume that it means there is no support for specifying a docker image reference in a cf app manifest.yml
cli/cf/manifest/manifest.go
Lines 167 to 223 in aa1c389
The text was updated successfully, but these errors were encountered: