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

There is no way to make persistent changes to machine #998

Closed
jdeslip opened this issue Oct 21, 2016 · 5 comments
Closed

There is no way to make persistent changes to machine #998

jdeslip opened this issue Oct 21, 2016 · 5 comments

Comments

@jdeslip
Copy link

jdeslip commented Oct 21, 2016

None of my changes to the workspace/machine seem to be saved when I stop and restart a workspace.

For example, if I use the terminal to apt-get install some software, or update the android SDK tools, all of these changes are lost the next time I start the workspace.

I gather the "snapshots" feature should enable these sorts of changes to be persistent, but I don't see any way to take a snapshot in the beta site. Is this a paid only feature? I see there is a greyed out "machine" menu - I can only guess what the options/commands are under that menu.

Codenvy Version: 5.0.0-M5

@jdeslip
Copy link
Author

jdeslip commented Oct 21, 2016

Well, I see now you can right click on the workspace name on the left and select "snapshot". But, it never seems to finish - but I guess this is reported in bug #918 already.

@TylerJewell
Copy link
Contributor

TylerJewell commented Oct 21, 2016

Hi jdeslip - this is a known issue. But there is a workaround. We have some hot fixes coming in M6, which is releasing soon. Here is the bug that was filed, and it's already merged into master - so the hot fix is coming.

#933
#918

@JamesDrummond
Copy link

@TylerJewell #933 is now closed and PR is merged. Can we close this issue and #918 ?

@TylerJewell
Copy link
Contributor

@JamesDrummond - I believe that we should wait for products to be released before we close an issue. PR merged is probably not suitable, especially if the original poster is a customer / outsider who cannot verify it.

@TylerJewell
Copy link
Contributor

All of these changes have been pushed into production.

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

3 participants