bryanforbes
commented
2 months ago I've run into a similar issue using buildroot with bind mounts. Some libraries/projects instruct libtool to make hard links to build files in a temporary directory before it links the entire project from that temporary directory and that seems to trip up OrbStack. If I reduce the CPU limit to 100% (1 core) and build those libraries individually after the build fails, then increase the CPU limit back to 800% (8 cores) and restart the build, everything works fine. I'm also under the impression that there's a race condition somewhere.
Reproduction steps:
- Ensure OrbStack is configured with a CPU limit of 200% or more (I recommend 800%)
git clone https://github.com/bryanforbes/batocera.linux.gitcd batocera.linuxgit checkout origin/bryanforbes/macos-buildgit submodule update --initmake build-docker-imageecho 'EXTRA_OPTS := BR2_CCACHE_INITIAL_SETUP=\"--max-size=50G\"' > batocera.mkmake x86_64-build
The build will fail at util-linux-libs, util-linux, or gmp with a message similar to the following:
/x86_64/host/lib/gcc/x86_64-buildroot-linux-gnu/13.3.0/../../../../x86_64-buildroot-linux-gnu/bin/ar: .libs/libgmp.lax/lt2-add.o: No such file or directory
make[3]: *** [Makefile:883: libgmp.la] Error 1
make[3]: Leaving directory '/x86_64/build/gmp-6.3.0'
make[2]: *** [Makefile:998: all-recursive] Error 1
make[2]: Leaving directory '/x86_64/build/gmp-6.3.0'
make[1]: *** [Makefile:788: all] Error 2
make[1]: Leaving directory '/x86_64/build/gmp-6.3.0'
make: *** [package/pkg-generic.mk:283: /x86_64/build/gmp-6.3.0/.stamp_built] Error 2
make: Leaving directory '/build/buildroot'
make: *** [x86_64-build] Error 2To get around this issue, when the build fails, I reduce the CPU limit to 100% and run make x86_64-pkg PKG=<package name here>, wait for it to finish, increase the limit to 800%, and re-run make x86_64-build.
houaq
niallnsec
Describe the bug
While attempting to compile a WASM version of Yara inside of a container, I think I have stumbled across an OrbStack bug.
When running a build with the build directory under the container filesystem everything completes successfully, however, if I run the build from a directory mounted from the host it fails with the error "No such file or directory" attempting to read a file which was just created. The file definitely exists. I am not sure how bests to gather debug info to validate whether it is caused by a bug in OrbStack or something else, but I have done my best to include everything needed to recreate the issue.
To Reproduce
docker buildx build --pull --load -t registry.example.com/emscripten:stable .Dockerfile
``` FROM ubuntu:noble AS builder ARG EMSCRIPTEN_VERSION=latest ENV EMSDK /emsdk RUN set -eux && \ apt-get -qq -y update && \ apt-get -qq install -y --no-install-recommends binutils build-essential ca-certificates file git \ python3 python3-pip curl cmake && \ mkdir -p "${EMSDK}" WORKDIR ${EMSDK} RUN set -eux && \ git clone https://github.com/emscripten-core/emsdk.git . && \ ./emsdk install ${EMSCRIPTEN_VERSION} && \ ./emsdk activate ${EMSCRIPTEN_VERSION} RUN set -eux && \ chmod 777 ${EMSDK}/upstream/emscripten && \ chmod -R 777 ${EMSDK}/upstream/emscripten/cache && \ echo "int main() { return 0; }" > hello.c && \ ${EMSDK}/upstream/emscripten/emcc -c hello.c && \ cat ${EMSDK}/upstream/emscripten/cache/sanity.txt RUN set -eux \ strip -s `which node` && \ rm -rf ${EMSDK}/upstream/emscripten/tests && \ rm -rf ${EMSDK}/upstream/emscripten/cache && \ mkdir ${EMSDK}/upstream/emscripten/cache && \ chmod -R 777 ${EMSDK}/upstream/emscripten/cache && \ rm -rf ${EMSDK}/.git && \ strip -s ${EMSDK}/upstream/bin/* FROM ubuntu:noble AS final COPY --from=builder /emsdk /emsdk COPY entrypoint.sh /usr/local/bin/entrypoint.sh ENV EMSDK /emsdk ENV PATH="${EMSDK}:${EMSDK}/upstream/emscripten:${EMSDK}/node/18.20.3_64bit/bin:${PATH}" RUN apt-get -qq -y update && \ apt-get -qq install -y --no-install-recommends \ sudo libxml2 ca-certificates python3 python3-pip wget curl zip unzip git git-lfs ssh-client \ build-essential make ant libidn12 cmake openjdk-11-jre-headless automake autoconf libtool \ pkg-config flex bison linux-headers-generic && \ chmod +x /usr/local/bin/entrypoint.sh && \ npm install -g typescript && \ apt-get -y clean && \ apt-get -y autoclean && \ apt-get -y autoremove && \ rm -rf /var/lib/apt/lists/* && \ rm -rf /var/cache/debconf/*-old && \ rm -rf /usr/share/doc/* && \ rm -rf /usr/share/man/?? && \ rm -rf /usr/share/man/??_* USER nobody:nogroup WORKDIR /src ENTRYPOINT ["/usr/local/bin/entrypoint.sh"] ```entrypoint.sh
``` #!/bin/bash set -e EMSDK_QUIET=1 source "${EMSDK}/emsdk_env.sh" exec "$@" ```Extract the attached libyara-wasm library code. libyara-wasm.tar.gz
Open a terminal in the extracted folder and start the docker build container
docker run --rm -it -v "$(pwd):/src" -u $(id -u):$(id -g) registry.example.com/emscripten:stable /bin/bashThe build should fail with the following error:
The build should complete successfully this time.
On the failed build, the file mentioned ".libs/libyara.lax/lt1-la-hash.o" does exist on disk when I check, and if you re-run the make command the build will resume and finish successfully. Since the error only occurs when build files are on a host mounted volume, it seems like there could be some kind of race condition at play.
Expected behavior
Both builds should complete successfully, regardless of the location of the build directory.
Diagnostic report (REQUIRED)
OrbStack info: Version: 1.7.0-rc2 Commit: 286173a3053ed7fcc0784d31ef8791886ad60224 (v1.7.0-rc2)
System info: macOS: 14.6.1 (23G93) CPU: arm64, 16 cores CPU model: Apple M3 Max Model: Mac15,9 Memory: 48 GiB
Full report: https://orbstack.dev/_admin/diag/orbstack-diagreport_2024-08-20T21-30-30.670595Z.zip
Screenshots and additional context (optional)
No response