Skip to content

migrate places data in incorrect volume #6

@eschrock

Description

@eschrock

Expected Behavior

If you migrate from an existing container, you should be able to push the commit and then clone from the remote repository.

Actual Behavior

Migrate will create a v1 volume, and clone will later fail when it can't find the v0 data it expects.

Steps to Reproduce the Problem

Migrate from a container. Push to an S3 bucket. Try to clone said bucket.

Version

0.3.0

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions