laantungir/fips
1
0
Fork 0
mirror of https://github.com/jmcorgan/fips.git synced 2026-10-05 19:18:25 +00:00
Code Issues Packages Projects Releases Wiki Activity

Keep the OpenWrt scenario harness's package scripts where docker can mount them

Browse Source 
The harness built the .apk's maintainer scripts into a directory from
mktemp -d and bind-mounted it into the busybox container. Under a service
with a private /tmp, as the CI workers run, the docker daemon resolves
that path in the host's /tmp, mounts an empty directory, and the three
apk scenarios fail for want of the scripts. Create the directory under
the checkout's target/ instead, which the daemon sees either way.
This commit is contained in:
Johnathan Corgan
2026-09-26 22:56:22 +00:00
parent 99e51c89a5
commit a8e8c547a7
1 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
testing/openwrt/maintainer-scripts-test.sh
+5 -1
View File
@@ -34,7 +34,11 @@ fi
# The .apk wraps the shared bodies for its upgrade path. package-test.sh builds
# the package on the host with the real build-apk.sh, checks what it registers,
# and leaves the four scripts here so the scenarios run exactly what ships.
APK_DIR="$(mktemp -d)" || { echo "openwrt-scripts: mktemp failed" >&2; exit 2; }
# The directory is bind-mounted into the container, so it must be one the docker
# daemon can see: under the checkout, not /tmp, which a service running with a
# private /tmp (as the CI workers do) does not share with the daemon.
mkdir -p "$PROJECT_ROOT/target" || { echo "openwrt-scripts: cannot create target/" >&2; exit 2; }
APK_DIR="$(mktemp -d "$PROJECT_ROOT/target/openwrt-apk.XXXXXX")" || { echo "openwrt-scripts: mktemp failed" >&2; exit 2; }
trap 'rm -rf "$APK_DIR"' EXIT
bash "$SCRIPT_DIR/package-test.sh" --keep "$APK_DIR"
rc=$?