terry/Arkie-Library-Frontend
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

ci: simplify runner disk resize check
Some checks failed
Deploy to Frontend Servers / deploy (push) Failing after 2s
Details

Browse Source
This commit is contained in:
TerryM
2026-06-09 01:10:32 +08:00
parent 0b8c4fe1f7
commit 5724d2b08c
2 changed files with 41 additions and 74 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
docs/deploy.md
View File

@@ -49,6 +49,18 @@ The workflow expects these Gitea secrets:
## Common failures
### Runner disk still shows the old EBS size
If the EC2 runner EBS volume was expanded but CI still reports a small root filesystem (for example `df -h /` still shows 8GB), the partition/filesystem has not grown yet. The deploy workflow runs an early `Ensure runner disk space` step that tries to grow `/` before installing dependencies:
```bash
sudo growpart <root-disk> <root-partition>
sudo resize2fs <root-partition> # ext filesystems
# or sudo xfs_growfs / # xfs filesystems
```
If that step says `growpart not installed`, install `cloud-utils-growpart` on the runner host and rerun the workflow.
### Node version is too old
The workflow pins Node.js 22 using `actions/setup-node`. This keeps the self-hosted runner from using an older system Node version during `npm ci`, tests, and build.