What's your CLI version?
1.11.1
Description & steps to reproduce
So, setting a persistent Directory which is meant (according to documentation) to persist across restarts and updates, results in the mount/fodler totally lost after service update. The mount is not attached to the new docker that is created after update.
Here a small PoC with screenshots so you can see the issue:
https://github.com/xavier-romero/scripts-pub/tree/main/kurtosis-poc/persistent-directory-issue
Desired behavior
Service update should attach the mount to the new updated docker so all our data is kept there as desired.
What is the severity of this bug?
Critical; I am blocked and Kurtosis is unusable for me because of this bug.
What area of the product does this pertain to?
CLI: the Command Line Interface
What's your CLI version?
1.11.1
Description & steps to reproduce
So, setting a persistent Directory which is meant (according to documentation) to persist across restarts and updates, results in the mount/fodler totally lost after service update. The mount is not attached to the new docker that is created after update.
Here a small PoC with screenshots so you can see the issue:
https://github.com/xavier-romero/scripts-pub/tree/main/kurtosis-poc/persistent-directory-issue
Desired behavior
Service update should attach the mount to the new updated docker so all our data is kept there as desired.
What is the severity of this bug?
Critical; I am blocked and Kurtosis is unusable for me because of this bug.
What area of the product does this pertain to?
CLI: the Command Line Interface