New issue
Advanced search Search tips

Issue 865207 link

Starred by 8 users

Issue metadata

Status: Available
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Feature


Participants' hotlists:
Hotlist-1


Sign in to add a comment

Provide user friendly UI for backup and restore of Crostini container

Reported by andrew.m...@gmail.com, Jul 18

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS x86_64 10866.1.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3486.0 Safari/537.36
Platform: 10866.1.0 (Official Build) dev-channel eve

Steps to reproduce the problem:
1. Enable linux support on chromebook
2. Install some apps or customize the container in some way
3. Powerwash the chromebook

What is the expected behavior?
There is an easy method to restore my container to its last state after a powerwash.

What went wrong?
Containers can be backed up and restored manually but the process is difficult and not user friendly.

Did this work before? N/A 

Chrome version: 69.0.3486.0  Channel: dev
OS Version: 10866.1.0
Flash Version: 

I imagine the following in settings after enabling linux support

1. A toggle to enable backups of your container to google drive
2. A button for "back up now"
3. A button for "restore container from backup"

Perhaps also auto-restore the container to it's last state upon enabling linux support after a powerwash if a suitable backup can be found?

This is a serious frustration in working with linux support as an end user at the moment. If something is going wrong I want to be able to powerwash my pixelbook and be up and running again quickly in the same state I was before. Right now after a powerwash I have to manually install all my linux apps and configuration which takes a lot of time and effort.
 
Components: -UI OS>Systems>Containers
Labels: Proj-Containers
Labels: -Pri-2 Pri-3
Status: Available (was: Unconfirmed)
Labels: -Type-Bug -Pri-3 Pri-2 Type-Feature
Please prioritize this. The inability to easily back up the container environment fundamentally affects its utility, and how ChromeOS behaves.

Sign in to add a comment