Skip to content

Epic: Full Workspace Backup #7719

@svenefftinge

Description

@svenefftinge
Contributor

Currently only the /workspace folder is backed up and preserved across workspace restarts, and from the prebuild. This is unintuitive, adds friction to the experience and is a source of issues for users.

The change to keep all workspace files is very core and should be available in all forms of the product: SaaS and Self-Hosted.

To make this happen there are a few technical challenges that we will need to solve first, particularly as self-hosted support that may use older kernel and containerd versions is required.

Notes from June 23, 2022
  • The biggest blocker we found was not the workdir location [related PR], but the interaction between overlayfs and shiftfs. TL;DR docker becomes unworkably slow if it needs to run on this setup because it falls back to VFS
  • idmapped mounts may be a solution, but they require recent Kernel versions which is a problem for self-hosted

Activity

axonasif

axonasif commented on Sep 7, 2021

@axonasif
Member

Anything on this yet?

mteam88

mteam88 commented on Sep 28, 2021

@mteam88

still waiting for development...

purkhusid

purkhusid commented on Oct 5, 2021

@purkhusid

Will this allow prebuilds to be bigger than 30gb?

shaal

shaal commented on Nov 1, 2021

@shaal
Contributor

Would this affect Snapshots feature?
(If yes, how can we avoid exposing things like private ssh key file at ~/.ssh/id_rsa)

transferred this issue fromon Jan 20, 2022
changed the title [-]Full Workspace Backup[/-] [+]Epic: Full Workspace Backup[/+] on Jan 20, 2022
stale

stale commented on Apr 21, 2022

@stale

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

added
meta: staleThis issue/PR is stale and will be closed soon
on Apr 21, 2022
shaal

shaal commented on Apr 21, 2022

@shaal
Contributor

Is there any update on this issue?

removed
meta: staleThis issue/PR is stale and will be closed soon
on Apr 21, 2022
sagor999

sagor999 commented on Apr 21, 2022

@sagor999
Contributor

This is superseded by this epic: #790
@atduarte should this one be closed now?

atduarte

atduarte commented on Apr 21, 2022

@atduarte
Contributor

I thought full workspace backup was out of scope for #7901 [1] and that the PVC would only contain the /workspace folder 🤔

If #7901 solves this, I would leave this open as an issue but reference the durability epic.

sagor999

sagor999 commented on Apr 21, 2022

@sagor999
Contributor

@atduarte you are right, it is indeed out of scope for that epic. I got confused a bit here. 😅

stale

stale commented on Sep 24, 2022

@stale

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

added
meta: staleThis issue/PR is stale and will be closed soon
on Sep 24, 2022
removed
meta: staleThis issue/PR is stale and will be closed soon
on Sep 26, 2022
a-b

a-b commented on Nov 17, 2022

@a-b

I'm wondering if some workaround is possible. What if we link folders like /home/linuxbrew/.linuxbrew to /workspace? Perhaps this could have some reflection in .gitopod.yml ?

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @shaal@svenefftinge@a-b@atduarte@loujaybee

        Issue actions

          Epic: Full Workspace Backup · Issue #7719 · gitpod-io/gitpod