@exagone313/dsh-podman 1.0.0 → 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.0";
2
- export declare const GIT_COMMIT = "bbf9727";
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.0";
6
- export const GIT_COMMIT = "bbf9727";
5
+ export const VERSION = "1.0.2";
6
+ export const GIT_COMMIT = "abf51e5";
package/docs/README.md ADDED
@@ -0,0 +1,45 @@
1
+ <!--
2
+ SPDX-FileCopyrightText: 2026 Elouan Martinet <exa@elou.world>
3
+
4
+ SPDX-License-Identifier: MIT
5
+ -->
6
+
7
+ # Documentation
8
+
9
+ [English](#english) | [中文](#中文)
10
+
11
+ ## English
12
+
13
+ - [Install DeepSeek Harness & dsh-podman with rootless Podman](install-dsh-and-dsh-podman.md)
14
+ — install dsh and dsh-podman as rootless Podman Quadlet services and verify
15
+ the setup.
16
+ - [Update](update.md) — pull new images, restart the services, and set up
17
+ automatic updates.
18
+ - [Architecture](architecture.md) — the plugin, the orchestrator and the guest
19
+ agents, and how workspaces map to pods and containers.
20
+ - [Configuration](configuration.md) — the `DSH_PODMAN_*` environment variables
21
+ per component, and the plugin's UI settings.
22
+ - [Usage](usage.md) — the model-facing tools, the Podman page, and the image
23
+ model.
24
+ - [Development](development.md) — build the plugin from this repository and run
25
+ it from a development checkout.
26
+ - [Development container setup prompt](development-prompt.md) — the prompt that
27
+ creates the development image, volume and container.
28
+ - [Uninstall](uninstall.md) — remove dsh-podman and the Quadlet units, and run
29
+ dsh without it.
30
+
31
+ ## 中文
32
+
33
+ - [使用 rootless Podman 安装 DeepSeek Harness 与 dsh-podman](install-dsh-and-dsh-podman.zh.md)
34
+ — 以 rootless Podman 的 Quadlet 服务安装 dsh 与 dsh-podman,并验证安装。
35
+ - [更新](update.zh.md) — 拉取新镜像、重启服务,并配置自动更新。
36
+ - [架构](architecture.zh.md) — 插件、orchestrator 与 guest
37
+ agent,以及工作区如何映射到 pod 与容器。
38
+ - [配置](configuration.zh.md) — 各组件读取的 `DSH_PODMAN_*`
39
+ 环境变量,以及插件的界面设置。
40
+ - [使用](usage.zh.md) — 面向模型的工具、Podman 页面以及镜像模型。
41
+ - [开发](development.zh.md) — 从本仓库构建插件,并在开发检出环境中运行。
42
+ - [开发容器设置提示词](development-prompt.zh.md) —
43
+ 用于创建开发镜像、卷与容器的提示词。
44
+ - [卸载](uninstall.zh.md) — 移除 dsh-podman 与 Quadlet
45
+ 单元,并在没有它的情况下运行 dsh。
@@ -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
 
@@ -197,5 +197,7 @@ host directory `<DSH_PODMAN_HOST_SOCKETS_ROOT>/<container>` is mounted at
197
197
  single per-workspace directory is mounted, a guest container never sees the
198
198
  orchestrator's `orchestrator.sock` nor any other workspace's socket directory.
199
199
  Both the control socket and each guest socket are created with mode `0600`, and
200
- both processes set a `0077` umask at startup so the socket is never briefly
201
- reachable between `bind` and `chmod`.
200
+ both processes create them under a `0077` umask so the socket is never briefly
201
+ reachable between `bind` and `chmod`. The guest agent then restores the
202
+ conventional `0022` mask, so the commands it runs create files `0644` and
203
+ directories `0755`.
@@ -177,5 +177,7 @@ Quadlet 会挂载 `%h/.dsh/dsh-podman/state`。orchestrator
177
177
  `<DSH_PODMAN_SOCKETS_ROOT>/<container>`。由于只挂载了这一个按工作区划分的目录,guest
178
178
  容器永远看不到 orchestrator 的
179
179
  `orchestrator.sock`,也看不到任何其他工作区的套接字目录。控制套接字和每个 guest
180
- 套接字都以权限模式 `0600` 创建,两个进程都会在启动时设置 `0077`
181
- umask,这样套接字在 `bind` 和 `chmod` 之间永远不会被短暂访问。
180
+ 套接字都以权限模式 `0600` 创建,两个进程都会在 `0077` umask
181
+ 下创建它们,这样套接字在 `bind` 和 `chmod` 之间永远不会被短暂访问。随后 guest
182
+ agent 会恢复常规的 `0022` umask,因此它运行的命令创建的文件为 `0644`、目录为
183
+ `0755`。
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@exagone313/dsh-podman",
3
- "version": "1.0.0",
3
+ "version": "1.0.2",
4
4
  "description": "Podman-backed execution for DeepSeek Harness (dsh).",
5
5
  "license": "MIT",
6
6
  "repository": {