Feature: preserve volumes list on plugin restart #7
Labels
enhancement
New feature or request
Comments
Closed
kolayne
added a commit
that referenced
this issue
May 31, 2023
Wrote a doc for which directories exist for volumes and how they are supposed to be managed. It will be used for storage implementation (#7)
kolayne
added a commit
that referenced
this issue
May 31, 2023
The plugin now determines the active mounts for a volume (not overlay) using the activemounts/ subdirectory corresponding to the volume. It resolves the race condition problem with parallel mounts/unmounts on the same volume. Gets us closer to fixing #7! However, not there yet, as we are still using go's `map`, which is thread-unsafe.
kolayne
added a commit
that referenced
this issue
Jun 2, 2023
- Removed the `volumes` field of `Driver`, instead introduced the metadata.json per-volume internal file, which currently stores the base directory path and the volatility. - Rewrote the methods that used the in-memory volume storage to use the filesystem instead. - Renamed dotBaseDir to `dotRootDir` and turned it into a field of `Driver`. Fixes #7. As far as I can see, fixes #15! The code is starting to get bulky, probably, restructuring is needed...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: