You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(compose): fail fast on unusable and missing external volumes
Named volumes now reach the container as a bind mount, so a name that
cannot become a host path, or an external volume that was never created,
has to stop the project before anything starts instead of surfacing as a
raw path error once some services are already up. The check mirrors the
external-network one and runs before networks or volumes are created.
- reject volume names containing ':', which would misparse inside the
-v source:destination argument
- resolveVolumeMounts takes the already-resolved backing directories
instead of re-deriving them from the project name and volume store
- drop the hand-written changelog entry; release-please owns that file
Copy file name to clipboardExpand all lines: CHANGELOG.md
-4Lines changed: 0 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,10 +12,6 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
12
12
***image inspect:**`mocker image inspect` and `mocker inspect --type=image` now return Docker-compatible `ImageInspect` JSON arrays with PascalCase keys instead of the previous lowercase `ImageInfo` object shape.
13
13
***MockerKit:**`ImageManager.inspect(_:platform:)` returns `ImageInspect` instead of `ImageInfo`.
14
14
15
-
### Bug Fixes
16
-
17
-
***compose:** named volumes are now mounted into containers, so their data survives `compose up --force-recreate` instead of silently living in the container layer and being discarded. Volumes resolve to their backing directory under the volume store (`<volumesPath>/<runtimeName>/_data`), matching Docker's behaviour; `down --volumes` still removes them.
0 commit comments