amsd-pipeline 2.0.5 → 2.0.6
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.
- package/install.sh +4 -1
- package/package.json +1 -1
package/install.sh
CHANGED
|
@@ -891,7 +891,10 @@ else
|
|
|
891
891
|
# ...and make them writable by the uid the CONTAINER runs as. Creating them as the host user
|
|
892
892
|
# is the whole fix under docker, where those uids are the same. Under rootless podman they are
|
|
893
893
|
# not, and the mkdir above reproduces the very failure this block exists to prevent.
|
|
894
|
-
|
|
894
|
+
# ./data is the container's own database — it may own that outright.
|
|
895
|
+
ensure_bind_mount_ownership "$LAUNCH_DIR/data"
|
|
896
|
+
# ./spool is the boundary the HOST runner writes; it must stay writable from both sides.
|
|
897
|
+
ensure_shared_bind_mount "$LAUNCH_DIR/spool"
|
|
895
898
|
|
|
896
899
|
_LD_PORT="$(grep -E '^LAUNCH_UI_PORT=' "$LAUNCH_DIR/.env" 2>/dev/null | tail -1 | cut -d= -f2)"
|
|
897
900
|
_LD_PORT="${_LD_PORT:-8099}"
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "amsd-pipeline",
|
|
3
|
-
"version": "2.0.
|
|
3
|
+
"version": "2.0.6",
|
|
4
4
|
"description": "Installer for the amsd-pipeline orchestration stack. Clones, packages and provisions the full stack with one command — no separate git clone step.",
|
|
5
5
|
"bin": {
|
|
6
6
|
"amsd-pipeline": "bin/amsd-pipeline.js"
|