@exagone313/dsh-podman 1.0.1 → 1.0.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,2 +1,2 @@
1
- export declare const VERSION = "1.0.1";
2
- export declare const GIT_COMMIT = "26bc28f";
1
+ export declare const VERSION = "1.0.2";
2
+ export declare const GIT_COMMIT = "abf51e5";
@@ -2,5 +2,5 @@
2
2
  //
3
3
  // SPDX-License-Identifier: MIT
4
4
  // Generated by scripts/generate-version.mjs; do not edit.
5
- export const VERSION = "1.0.1";
6
- export const GIT_COMMIT = "26bc28f";
5
+ export const VERSION = "1.0.2";
6
+ export const GIT_COMMIT = "abf51e5";
@@ -103,10 +103,13 @@ process working directory, so a discovery listing the harness starts with an
103
103
  absolute search root runs from that root: `glob`'s `pattern` then anchors to its
104
104
  `path` while the printed paths stay absolute.
105
105
 
106
- Project mounts resolve through symlinks and are confined to the projects root,
107
- so a symlink inside a writable project cannot redirect the bind mount to a path
108
- outside it. Symlinks with absolute targets are never followed; name the other
109
- project directly instead.
106
+ Project mounts must contain no symlink component and are confined to the
107
+ projects root, so a symlink inside a writable project can neither redirect the
108
+ bind mount to a path outside it nor make the path the orchestrator validates
109
+ differ from the path podman mounts. A new project mount is also refused while
110
+ another container holds a read-write mount that is a strict ancestor of it: that
111
+ container's agent could otherwise rename a component of the new path to a
112
+ symlink before podman resolves it.
110
113
 
111
114
  ## Guest agent and daemons
112
115
 
@@ -82,8 +82,11 @@ UUID),因此其容器共享一个网络命名空间。每个工作区都有
82
82
  启动的目录列举以绝对搜索根目录运行时,它会从该根目录运行:此时 `glob` 的
83
83
  `pattern` 锚定到其 `path`,而打印出的路径保持绝对。
84
84
 
85
- 项目挂载会解析符号链接并被限制在 projects root
86
- 内,因此可写项目中的符号链接不能将绑定挂载重定向到其外部的路径。带有绝对目标的符号链接永远不会被跟随;请直接命名另一个项目。
85
+ 项目挂载不得包含任何符号链接组件,并被限制在 projects root
86
+ 内,因此可写项目中的符号链接既不能将绑定挂载重定向到其外部的路径,也不能让
87
+ orchestrator 校验的路径与 podman
88
+ 实际挂载的路径不一致。当另一个容器持有某个新挂载路径的严格祖先目录的读写挂载时,该新挂载也会被拒绝:否则那个容器的
89
+ agent 就能在 podman 解析之前把新路径的某个组件改名为符号链接。
87
90
 
88
91
  ## Guest agent 与守护进程
89
92
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@exagone313/dsh-podman",
3
- "version": "1.0.1",
3
+ "version": "1.0.2",
4
4
  "description": "Podman-backed execution for DeepSeek Harness (dsh).",
5
5
  "license": "MIT",
6
6
  "repository": {