What's special about V2 Environments?
Our next generation of Compute Environments help you do reproducible research at scale.
- Environments are now versioned and allow you to re-run past computations with exactly the same compute environment
- Our backend infrastructure will build your environment once and cache leading to better performance and user experience
- Environments are now their own top level entity, and are easier to discover and manage.
Migrating your V1 environment
Step 1: Re-create your V1 environment as V2
Navigate over to your V1 environment definition page (through the Manage V1 Environments link on Project settings, or through the Admin interface) and click on the "Recreate as V2" button. You will be taken to the Overview page of your new V2 environment. Navigate over to the Revisions tab to watch the progress of your environment build. Once it finishes building, you can proceed to Step 2.
You can only do this for non-global environments and if you are the owner of the V1 environment or an admin.
Note: Sometimes the build may fail if the original base image of the V1 environment is too old and has many layers. If this is the case, flatten your base image and try rebuilding the environment. If you see an error like this:
open /var/lib/docker/overlay/<long guid>/root/.wh..wh.plnk/498.
4220381: no such file or directory
please contact firstname.lastname@example.org.
Step 2: Use/test your V2 environment
You can now start using your V2 environment. If you go to your Project's Settings page you can set your project's environment to the new environment.
Step 3: Migrate all projects using V1 to V2
After you've tested your V2 environment, you can use the Migrate button to move all remaining projects to use the new V2 environment.
Step 4: Archive
You can archive your V1 environment. This will now be read-only and will be retained only for traceability purposes.