Release image upload: the image directory belongs to the deploy user
CI / go (push) Successful in 53s
CI / agent (push) Successful in 4s
CI / site (push) Successful in 2s

The image job built as root and uploaded as the deploy user, so
publish-image.sh could not write SHA256SUMS (v0.3.0's image job failed).
The job hands the directory over after the build, and publish-image.sh
checks the SHA256SUMS build-image.sh wrote instead of rewriting it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Ilker ManapandClaude Opus 5.5 committed 2026-10-31 09:32:54 +01:00
1 parent ea47438f81
commit ff0de7e0b2
2 files changed
+3 -1

No files matched your search

+1
View File
@@ -97,6 +97,7 @@ jobs:
ssh "$USER@$HOST" "sudo rm -rf $W && mkdir -p $W/src"
scp -q -r agent deploy/publish-image.sh "$USER@$HOST:$W/src/"
ssh "$USER@$HOST" "sudo env AUTHKEYS= BUILD=$W/build OUT=$W/image bash $W/src/agent/build-image.sh > $W/build.log 2>&1 || { tail -40 $W/build.log; exit 1; }; tail -5 $W/build.log"
ssh "$USER@$HOST" "sudo chown -R \$(id -u):\$(id -g) $W/image" # the upload runs as the deploy user
# refuse an image that lets someone in (a listing that fails refuses too)
ssh "$USER@$HOST" "sudo unsquashfs -l $W/image/filesystem.squashfs > $W/files" ||
{ echo "::error::cannot list the image" >&2; exit 1; }