Redirect cargo-leptos's tool cache out of act-runner-bare's StateDirectory
Deploy / deploy (push) Failing after 27s
Deploy / deploy (push) Failing after 27s
wasm-bindgen/wasm-opt binaries cargo-leptos downloads under XDG_CACHE_HOME ended up owned by the kernel's overflow "nobody" uid inside systemd's StateDirectory for this unit - a quirk of that specific path, not anything about our shared-cache setup (CARGO_TARGET_DIR elsewhere is owned correctly). Pointing XDG_CACHE_HOME at our own shared /var/local/leptos-cache sidesteps it; verified with a clean checkout + a from-scratch env matching the workflow's exactly.
This commit is contained in:
@@ -29,6 +29,15 @@ jobs:
|
|||||||
SCCACHE_DIR: /var/local/sccache
|
SCCACHE_DIR: /var/local/sccache
|
||||||
SCCACHE_SERVER_PORT: "4228"
|
SCCACHE_SERVER_PORT: "4228"
|
||||||
CARGO_TARGET_DIR: /var/local/cargo-target
|
CARGO_TARGET_DIR: /var/local/cargo-target
|
||||||
|
# cargo-leptos's own downloaded tools (wasm-bindgen, wasm-opt) cache
|
||||||
|
# under $XDG_CACHE_HOME - left at its default that resolves inside
|
||||||
|
# this unit's systemd StateDirectory, files it creates there end up
|
||||||
|
# owned by the kernel's overflow "nobody" uid instead of the
|
||||||
|
# runner's own dynamic uid (a StateDirectory quirk, not something
|
||||||
|
# in our control), so a later run can't execute what an earlier run
|
||||||
|
# downloaded. Redirecting it to our own known-good shared dir avoids
|
||||||
|
# that entirely.
|
||||||
|
XDG_CACHE_HOME: /var/local/leptos-cache
|
||||||
steps:
|
steps:
|
||||||
- uses: actions/checkout@v4
|
- uses: actions/checkout@v4
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user