-
Notifications
You must be signed in to change notification settings - Fork 91
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
volumes from one suite are added to all subsequent suites #152
Labels
Comments
Additional note: If I run the suites one at a time, they work as expected. |
seeing similar behavior, have two suites defined, each with it's own volumes
getting exception when running test / converge on both
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
Adding a volume in one suite's driver config adds it to all the suites that follow it in
.kitchen.yml
.Versions
Reproducing
Create the following
.kitchen.yml
in an empty directory and runkitchen create
:Expected Results
kitchen create
executes successfullysuite1-alpine
container does not have any volumes mountedsuite2-alpine
container has the volumesuite2_vol
mounted at/vol
suite3-alpine
container does not have any volumes mountedsuite4-alpine
container has the volumesuite4_vol
mounted at/vol
Actual Results
kitchen create
fails with the error message:Failed to complete #create action: [Duplicate mount point: /vol] on suite4-alpine
suite1-alpine
container does not have any volumes mountedsuite2-alpine
container has the volumesuite2_vol
mounted at/vol
suite3-alpine
container has the volumesuite2_vol
mounted at/vol
suite4-alpine
container doees not existThe text was updated successfully, but these errors were encountered: