-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Verify if a volume is active. #129
Verify if a volume is active. #129
Conversation
I think the second screenshot's behavior is the target of #89, so we can ignore that for this PR. Reviewing the rest of the PR now. Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work! Just a few quick notes
Co-authored-by: Sara Bine <sara@tighten.co>
Hi @mattstauffer , thanks for your review. A made some review and a merge main in my branch to avoid conflicts. |
Hi @mattstauffer now PR is updated. This PR needs #157 . |
@danielebarbaro Great--taking a look now. Thanks! |
Looks great. Thanks so much @danielebarbaro! |
Hi @mattstauffer , this maybe solve #123 .
I used "maybe" because I've a doubt.

At the moment I checked with
docker ps -a --filter volume=volume_name
that a volume exist and the result is:So when user chose an existing container takeout return an error until user chose a unique name container.
Do you want to handle ,in some way, also this behaviour?