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

Managing machine snapshots #349

Closed
lidoma opened this issue Jul 5, 2016 · 3 comments
Closed

Managing machine snapshots #349

lidoma opened this issue Jul 5, 2016 · 3 comments

Comments

@lidoma
Copy link

lidoma commented Jul 5, 2016

I take a machine snapshots to hold new state of machine after installing packages. Where these snapshot files stored? Can we have a history of taken snapshots?

And what's the use case of Source URL of machine?

@ghost
Copy link

ghost commented Jul 6, 2016

@lidoma Snapshots are created at Machine > Create Snapshot on Operations Perspective (switcher in the top right corner).

Snapshots are stored in a Docker registry that we run in our infrastructure.

Can you elaborate on source URL of a machine?

@lidoma
Copy link
Author

lidoma commented Jul 6, 2016

@eivantsov Please let me explain what i have in mind by example. I take, for instance, three snapshots from three different machine states. Can i see a list of these three snapshots according to their taken date which i can choose one of them? As I found out, we can just take one snapshot and restore just that.
I can see a machine property in Targets dialog window which called Source URL? For instance,

beta.codenvy.com:5000/0glom19q7sxxxxxx:latest@sha256:85e216cd44b5ce292b01e9ef4f5cf3d61a34f21ec61a8e9afab5c7bf53xxxxxx

What's the use case of this URL?

@ghost
Copy link

ghost commented Jul 7, 2016

@lidoma this is the URL to a snapshot image that is pulled.

Codenvy uses the latest snapshot made, and there's no list of available snapshots since when a new snapshot is made, the old one gets deleted.

@ghost ghost added the kind/question label Jul 11, 2016
@ghost ghost closed this as completed Jul 18, 2016
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant