Skip to content
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

Check docker/volume compatibility with remotes #34

Open
eschrock opened this issue Sep 27, 2019 · 0 comments
Open

Check docker/volume compatibility with remotes #34

eschrock opened this issue Sep 27, 2019 · 0 comments
Assignees
Labels
Priority: Important Address ahead of normal issues Type: Bug Something isn't working

Comments

@eschrock
Copy link
Contributor

Expected Behavior

If I try to pull from a remote that is incompatible with my current repository, I should get a clean error.

Actual Behavior

We'll happily try to pull down volumes even if they don't make sense (e.g. cloning a "v1" that doesn't exist).

Steps to Reproduce the Problem

Create a repo with multiple volumes (like mongo) and push to a remote. Create a new repo with a single volume (like postgres), add the remote, and pull.

Version

0.3.1

Additional Information

There is some ambiguity about what "compatible" means. At a mimum, I'd say it should be that number of volumes, and their mappings into the container, is consistent. A slightly more strict version would be that they are derived from the same image tag, though without a way to control that it may be annoying. A super strict version is that the docker config has to match exactly.

@eschrock eschrock added the Type: Bug Something isn't working label Sep 27, 2019
@mcred mcred added the Priority: Important Address ahead of normal issues label Oct 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: Important Address ahead of normal issues Type: Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants