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

Set some default remotes #114

Closed
stgraber opened this issue Dec 5, 2014 · 4 comments
Closed

Set some default remotes #114

stgraber opened this issue Dec 5, 2014 · 4 comments
Assignees
Labels
Feature New feature, not a bug
Milestone

Comments

@stgraber
Copy link
Contributor

stgraber commented Dec 5, 2014

On a system that has lxd installed, on first start of lxc, the following remotes should be added:

  • local -> unix+lxd://var/lib/lxd/socket
  • images -> https+registry://registry.linuxcontainers.org

In this case, the local remote should be marked as the default.

On a system with only lxc installed and no daemon, only the images remote should be added on first start.

In this case, no remotes should be set as default and the first one added by the user should then be marked as the default.

@stgraber stgraber added Feature New feature, not a bug Release critical labels Dec 5, 2014
@stgraber stgraber added this to the lxd-0.1 milestone Dec 5, 2014
@kunalkushwaha
Copy link

One doubt regarding this, for images operations, lxc will communicate to registry-server via lxd right?
The routes defined in https://github.com/lxc/lxd/blob/master/client.go#L146 is same which you are referred in this issue ?

@stgraber
Copy link
Contributor Author

stgraber commented Dec 9, 2014

No, lxc directly talks to the registry. It then presents the list of images to the user and when the user starts a container from one of those, then the contact information for that image is sent over to lxd in the create call.

@kunalkushwaha
Copy link

Okay got it. I am working on same, had partially implemented via lxd , will fix it.

@stgraber
Copy link
Contributor Author

This issue isn't really relevant anymore as non-lxd remotes are no more and we already have lxc talking to the local lxd.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature New feature, not a bug
Projects
None yet
Development

No branches or pull requests

3 participants