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

Problem with VM (resolved) #3436

Closed
matmat94 opened this Issue Dec 31, 2017 · 2 comments

Comments

Projects
None yet
3 participants
@matmat94

Latest stable release downloaded on 31/12/12

I installed OS with default options.
Then I change 'personal' VM to Debian 8.
In 'personal' VM I run apt-get update then apt-get upgrade in order to make Google Chrome work.
I shutdown the VM then restart it.
Everything disappeared. Even worse, after an apt-get update the google-chrome-stable package can't be found but it was found in the first place as if in between something changed the apt repositories list.
It's very frustrating as I don't understand one bit of why all of this happened.
When VM are shut down, are they reset ? Why in the world would someone want that behavior ?
Plus I guess there are disposable VMs for a reason.
Also, a connection to the Tor network could not be made despite multiple retries despite the fact that Internet was working perfectly.
I was very excited to use this OS but now I just want to throw it away.

Please tell me I made a mistake somewhere while installing the OS or did something bad somewhere. I would love to use this OS which seemed perfect in the first place for people who care about security/privacy.

Thanks in advance and sorry for the angryness...

@matthazinski

This comment has been minimized.

Show comment
Hide comment
@matthazinski

matthazinski Dec 31, 2017

In 'personal' VM I run apt-get update then apt-get upgrade in order to make Google Chrome work.
I shutdown the VM then restart it.
Everything disappeared. It's very frustrating as I don't understand one bit of why all of this happened.
When VM are shut down, are they reset ? Why in the world would someone want that behavior ?

Plus I guess there are disposable VMs for a reason.

This is intentional. Each qube's root filesystem is a read-only mount of the corresponding TemplateVM, but (except for disposable VMs) the home directory is preserved between reboots. Installing software outside of your home directory must be done in the TemplateVM. The getting started guide has more details.

Also, a connection to the Tor network could not be made despite multiple retries despite the fact that Internet was working perfectly.

More information is needed to debug this. You may have more success if you open a new issue adhering to the issue template and share details of your network topology and any relevant logs.

In 'personal' VM I run apt-get update then apt-get upgrade in order to make Google Chrome work.
I shutdown the VM then restart it.
Everything disappeared. It's very frustrating as I don't understand one bit of why all of this happened.
When VM are shut down, are they reset ? Why in the world would someone want that behavior ?

Plus I guess there are disposable VMs for a reason.

This is intentional. Each qube's root filesystem is a read-only mount of the corresponding TemplateVM, but (except for disposable VMs) the home directory is preserved between reboots. Installing software outside of your home directory must be done in the TemplateVM. The getting started guide has more details.

Also, a connection to the Tor network could not be made despite multiple retries despite the fact that Internet was working perfectly.

More information is needed to debug this. You may have more success if you open a new issue adhering to the issue template and share details of your network topology and any relevant logs.

@matmat94

This comment has been minimized.

Show comment
Hide comment
@matmat94

matmat94 Dec 31, 2017

Oh alright it makes a lot more sense now; I should have read the guide first.
I'll make another issue adhering to the template about the Tor problem.
Thank you for your reply.

Oh alright it makes a lot more sense now; I should have read the guide first.
I'll make another issue adhering to the template about the Tor problem.
Thank you for your reply.

@matmat94 matmat94 closed this Dec 31, 2017

@matmat94 matmat94 changed the title from Completely buggy OS [BUGS] to Problem with VM (resolved) Dec 31, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment