Skip to content
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

Proposal feat(controller): allow deis pull from deis-registry #32

Open
Cryptophobia opened this issue Mar 20, 2018 · 5 comments
Open

Proposal feat(controller): allow deis pull from deis-registry #32

Cryptophobia opened this issue Mar 20, 2018 · 5 comments
Labels

Comments

@Cryptophobia
Copy link
Member

From @deis-admin on January 19, 2017 23:44

From @aledbf on March 20, 2015 1:7

Something like

deis pull —from-internal-registry application-a:version -a application-b

to allow the deploy in application-b from application-a without using internal ip addresses

Copied from original issue: deis/deis#3341

Copied from original issue: deis/controller#1227

@Cryptophobia
Copy link
Member Author

From @deis-admin on January 19, 2017 23:44

From @mboersma on March 26, 2015 22:2

This could also be a use case for deis push, and we would rather add new functionality to that than on top of deis pull I think.

@Cryptophobia
Copy link
Member Author

From @deis-admin on January 19, 2017 23:44

From @babarinde on April 15, 2015 12:40

This s really a needed feature.
Thanks for the work
@aledbf @mboersma
Can I Pull (and Push ) from the deis-registry from a coreos node in the cluster ?
Also if i do deis pull example.com:5000/image:v2 -a app
Is this good practice as against using the Internal Ip of the registry

@Cryptophobia
Copy link
Member Author

From @deis-admin on January 19, 2017 23:44

From @aledbf on April 15, 2015 12:52

@babarinde the idea of this proposal is to avoid the search of the ip inside the cluster where the registry is running.

Can I Pull (and Push ) from the deis-registry from a coreos node in the cluster ?

yes, just use the ip inside the cluster docker pull <ip>:5000/app:vXX

Also if i do deis pull example.com:5000/image:v2 -a app

that's the idea of deis pull :) (http://deis.io/demo-deis-pull-in-action/)

Is this good practice as against using the Internal Ip of the registry

I don't know if is a "good practice" but for me solves a huge problem (have 1 app as "template" and N "copies", is useful to pull from the cluster without any external connection)

@Cryptophobia
Copy link
Member Author

From @deis-admin on January 19, 2017 23:44

From @babarinde on April 16, 2015 7:23

@aledbf

that's the idea of deis pull :) (http://deis.io/demo-deis-pull-in-action/)

How does deis resolve example.com:5000 to the internal IP of the registry when the registry is not scaled to 3?

@Cryptophobia
Copy link
Member Author

From @deis-admin on January 19, 2017 23:44

From @aledbf on April 16, 2015 13:9

How does deis resolve example.com:5000 to the internal IP of the registry when the registry is not scaled to 3?

If you do not specify a full hostname:port deis pull will use the public docker registry to retrieve the image. Remember that this is a proposal to change that behavior.

Now how deis resolve the registry if there's more than one is the easy part :)
check with etcdctl ls --recursive /deis/registry the key /deis/registry/host contains the registry that is acting as "master" (you can have multiple registries in the cluster but only one is used to pull/push)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant