[Q] How can I apply a workaround for "32bit build within a 64bit host using qemu"? #172
Comments
@iav I need more info. Please create a proper bug report. |
It's not a bug. At least — not your program bug, that can be "fixed". It's hard to reproduce, but very often occurs on wps hostings like aws, azure etc. For example — I got it when I try to run your action, and got that situation: Note line 813:
Don't trust this "spurious network error" — there nothing about network. In case this error occures "on local machine" — it can be solved providing smaller filesystem, where 64 bit inodes will not use, like
or with tmpfs like
but again — how can I replace docker work storage on a shared hosting runner? |
I found.
|
There are a but "32bit build within a 64bit host using qemu".
More details and workaround here uraimo/run-on-arch-action#9, rust-lang/cargo#7451 → https://lkml.org/lkml/2018/12/28/461
In my case I need to have a rust builder container for armv7 target have tmpfs or other 32/64 bit error-free fs for /usr/local/cargo/registry and, maybe, /root/.cargo/ folders.
I it possible to apply something like
for all builder container?
The text was updated successfully, but these errors were encountered: