@exagone313/dsh-podman 1.0.1 → 1.0.3

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.3";
2
+ export declare const GIT_COMMIT = "46f18d1";
@@ -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.3";
6
+ export const GIT_COMMIT = "46f18d1";
@@ -103,10 +103,15 @@ 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. Two containers may also not hold nested
110
+ project mounts when the outer one is read-write, whichever was created first:
111
+ the outer container's agent could otherwise rename a component of the inner path
112
+ to a symlink before podman resolves it, on a create or on any later restart. A
113
+ container being replaced is stopped before its mounts are resolved again, so its
114
+ own processes cannot race the create either.
110
115
 
111
116
  ## Guest agent and daemons
112
117
 
@@ -148,6 +153,13 @@ the read-write mounts forced read-only before running the tool. The harness's
148
153
  `sandbox_permissions` escalation is granted without prompting for the same
149
154
  reason: the widening it asks for has no effect here.
150
155
 
156
+ Read-only is enforced on the container a tool targets, not on the whole
157
+ workspace. Other containers in the same workspace may still hold read-write
158
+ mounts and run daemons, and a workspace's containers share a pod network
159
+ namespace, so a command that is allowed under read-only can reach a sibling
160
+ container over localhost and have it write. Read-only confines the session's own
161
+ container; it is not a guarantee that nothing in the workspace can be written.
162
+
151
163
  Recreating a container or shutting down the orchestrator first asks the
152
164
  container's guest agent to gracefully stop its daemons (SIGTERM, ~10s grace)
153
165
  before podman tears the container down.
@@ -82,8 +82,12 @@ 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
90
+ 解析之前(创建时或之后任何一次重启时)把内层路径的某个组件改名为符号链接。被替换的容器会先停止,再重新解析其挂载,因此它自己的进程也无法与创建过程竞争。
87
91
 
88
92
  ## Guest agent 与守护进程
89
93
 
@@ -120,6 +124,10 @@ PATH。
120
124
  按钮渲染该提示——并在获准后以强制只读的挂载重建容器,再运行该工具。出于同样的原因,harness
121
125
  的 `sandbox_permissions` 升权会被直接授予而不询问:它请求的放宽在此处没有效果。
122
126
 
127
+ 只读模式是针对工具所作用的那个容器执行的,而非整个工作区。同一工作区中的其他容器仍可持有读写挂载并运行守护进程,而且工作区内的容器共享一个
128
+ pod 网络命名空间,因此在只读模式下被允许的命令可以通过 localhost
129
+ 访问同级容器并让其写入。只读模式只约束会话自身的容器,并不保证工作区内没有任何东西可被写入。
130
+
123
131
  重新创建容器或关闭 orchestrator 时,会先要求容器的 guest agent
124
132
  优雅地停止其守护进程(SIGTERM,约 10 秒宽限期),然后 podman 才会拆除该容器。
125
133
 
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.3",
4
4
  "description": "Podman-backed execution for DeepSeek Harness (dsh).",
5
5
  "license": "MIT",
6
6
  "repository": {