Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix deneb docker builds #3929

Closed
realbigsean opened this issue Jan 27, 2023 · 4 comments
Closed

Fix deneb docker builds #3929

realbigsean opened this issue Jan 27, 2023 · 4 comments
Assignees
Labels

Comments

@realbigsean
Copy link
Member

realbigsean commented Jan 27, 2023

Description

We can't create multi-arch images in our CI because of the following failure in aarch64. It looks like it has to do with c-kzg

 error: linking with `aarch64-linux-gnu-gcc` failed: exit status: 1
  |
  = note: "aarch64-linux-gnu-gcc" "/tmp/rustcmkF3IZ/symbols.o" "/target/aarch64-unknown-linux-gnu/maxperf/deps/lighthouse-fa0748deceb6a62e.lighthouse.ff594d1a-cgu.0.rcgu.o" "-Wl,--as-needed" "-L" "/target/aarch64-unknown-linux-gnu/maxperf/deps" "-L" "/target/maxperf/deps" "-L" "/target/aarch64-unknown-linux-gnu/maxperf/build/blst-c4fa61d9db1d5d9c/out" "-L" "/target/aarch64-unknown-linux-gnu/maxperf/build/ring-d5379684085ce144/out" "-L" "/target/aarch64-unknown-linux-gnu/maxperf/build/c-kzg-b8cc815cb26fd4aa/out" "-L" "/target/aarch64-unknown-linux-gnu/maxperf/build/c-kzg-b8cc815cb26fd4aa/out" "-L" "/target/aarch64-unknown-linux-gnu/maxperf/build/libsqlite3-sys-4efd44bceaf497c6/out" "-L" "/target/aarch64-unknown-linux-gnu/maxperf/build/libz-sys-d5a2fb5fdb1c5729/out/lib" "-L" "/target/aarch64-unknown-linux-gnu/maxperf/build/libz-sys-d5a2fb5fdb1c5729/out/lib" "-L" "/target/aarch64-unknown-linux-gnu/maxperf/build/openssl-sys-6484d52495f21a19/out/openssl-build/install/lib" "-L" "/target/aarch64-unknown-linux-gnu/maxperf/build/leveldb-sys-8ddb10b39278f84b/out/lib" "-L" "/target/aarch64-unknown-linux-gnu/maxperf/build/mdbx-sys-6ac38cea22df0899/out" "-L" "/rust/lib/rustlib/aarch64-unknown-linux-gnu/lib" "-Wl,-Bstatic" "/tmp/rustcmkF3IZ/libmdbx_sys-6a5aadc2e0568eec.rlib" "/tmp/rustcmkF3IZ/liblibz_sys-34383be1728b1fcb.rlib" "/tmp/rustcmkF3IZ/libleveldb_sys-f763a94d051e148b.rlib" "/tmp/rustcmkF3IZ/libopenssl_sys-2542b6117bc085c6.rlib" "/tmp/rustcmkF3IZ/liblibsqlite3_sys-636477213e2e1f4e.rlib" "/tmp/rustcmkF3IZ/libc_kzg-6053850523939b06.rlib" "/tmp/rustcmkF3IZ/libblst-a8acb38f67b60d12.rlib" "/tmp/rustcmkF3IZ/libring-5f9be5d7b4f31a9b.rlib" "/rust/lib/rustlib/aarch64-unknown-linux-gnu/lib/libcompiler_builtins-0222020c3eea44f8.rlib" "-Wl,-Bdynamic" "-lstdc++" "-lgcc_s" "-lutil" "-lrt" "-lpthread" "-lm" "-ldl" "-lc" "-Wl,--eh-frame-hdr" "-Wl,-znoexecstack" "-L" "/rust/lib/rustlib/aarch64-unknown-linux-gnu/lib" "-o" "/target/aarch64-unknown-linux-gnu/maxperf/deps/lighthouse-fa0748deceb6a62e" "-Wl,--gc-sections" "-pie" "-Wl,-zrelro,-znow" "-Wl,-O1" "-nodefaultlibs"
  = note: /usr/lib/gcc-cross/aarch64-linux-gnu/5/../../../../aarch64-linux-gnu/bin/ld: /tmp/rustcmkF3IZ/libc_kzg-6053850523939b06.rlib(c_kzg_4844.o): Relocations in generic ELF (EM: 62)
          /usr/lib/gcc-cross/aarch64-linux-gnu/5/../../../../aarch64-linux-gnu/bin/ld: /tmp/rustcmkF3IZ/libc_kzg-6053850523939b06.rlib(c_kzg_4844.o): Relocations in generic ELF (EM: 62)
          /tmp/rustcmkF3IZ/libc_kzg-6053850523939b06.rlib: error adding symbols: File in wrong format
          collect2: error: ld returned 1 exit status
          

error: could not compile `lighthouse` due to previous error
make: *** [Makefile:71: build-aarch64-portable] Error 101
Error: Process completed with exit code 2.
@realbigsean realbigsean changed the title Fix aarch64 builds on the EIP4844 branch Fix aarch64 docker builds on the eip4844 branch Jan 27, 2023
@realbigsean realbigsean self-assigned this Jun 29, 2023
@realbigsean realbigsean changed the title Fix aarch64 docker builds on the eip4844 branch Fix deneb docker builds Jun 29, 2023
@realbigsean
Copy link
Member Author

New issues in our automated builds, trying to see if I can reproduce it. Looks like it has to do with the libclang version

  --- stderr
  Using LIB_PREFIX=ckzg
  Using FIELD_ELEMENTS_PER_BLOB=4096
  thread 'main' panicked at '
  A `libclang` function was called that is not supported by the loaded `libclang` instance.

      called function = `clang_getTranslationUnitTargetInfo`
      loaded `libclang` instance = 3.9.x

  This crate only supports `libclang` 3.5 and later.
  The minimum `libclang` requirement for this particular function can be found here:
  https://docs.rs/clang-sys/latest/clang_sys/clang_getTranslationUnitTargetInfo/index.html

  Instructions for installing `libclang` can be found here:
  https://rust-lang.github.io/rust-bindgen/requirements.html
  ', /cargo/registry/src/index.crates.io-6f17d22bba15001f/clang-sys-1.6.1/src/lib.rs:1735:1
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
make: *** [Makefile:76: build-x86_64-portable] Error 101

@realbigsean
Copy link
Member Author

Ok now, it looks like we're OOMing on aarch64 builds. I tested cross building on an ubuntu server with 8GB of RAM and it similarly OOMed. The default github actions runner has 7GB of RAM. I tested out the cross build on a 16GB server and it worked fine.

@realbigsean
Copy link
Member Author

we can resolve this when this is merged #4115

@jimmygchen
Copy link
Member

#4115 has been merged to unstable. This should be unblocked as soon as we merge latest unstable into deneb branch.

bors bot pushed a commit that referenced this issue Sep 20, 2023
## Issue Addressed

We're OOM'ing on Docker builds on the Deneb branch #3929

Are we ok to self host automated docker builds?


Co-authored-by: realbigsean <seananderson33@gmail.com>
Co-authored-by: realbigsean <sean@sigmaprime.io>
Co-authored-by: antondlr <anton@delaruelle.net>
bors bot pushed a commit that referenced this issue Sep 20, 2023
## Issue Addressed

We're OOM'ing on Docker builds on the Deneb branch #3929

Are we ok to self host automated docker builds?


Co-authored-by: realbigsean <seananderson33@gmail.com>
Co-authored-by: realbigsean <sean@sigmaprime.io>
Co-authored-by: antondlr <anton@delaruelle.net>
bors bot pushed a commit that referenced this issue Sep 21, 2023
## Issue Addressed

We're OOM'ing on Docker builds on the Deneb branch #3929

Are we ok to self host automated docker builds?


Co-authored-by: realbigsean <seananderson33@gmail.com>
Co-authored-by: realbigsean <sean@sigmaprime.io>
Co-authored-by: antondlr <anton@delaruelle.net>
bors bot pushed a commit that referenced this issue Sep 21, 2023
## Issue Addressed

We're OOM'ing on Docker builds on the Deneb branch #3929

Are we ok to self host automated docker builds?


Co-authored-by: realbigsean <seananderson33@gmail.com>
Co-authored-by: realbigsean <sean@sigmaprime.io>
Co-authored-by: antondlr <anton@delaruelle.net>
bors bot pushed a commit that referenced this issue Sep 21, 2023
## Issue Addressed

We're OOM'ing on Docker builds on the Deneb branch #3929

Are we ok to self host automated docker builds?


Co-authored-by: realbigsean <seananderson33@gmail.com>
Co-authored-by: realbigsean <sean@sigmaprime.io>
Co-authored-by: antondlr <anton@delaruelle.net>
bors bot pushed a commit that referenced this issue Sep 21, 2023
## Issue Addressed

We're OOM'ing on Docker builds on the Deneb branch #3929

Are we ok to self host automated docker builds?


Co-authored-by: realbigsean <seananderson33@gmail.com>
Co-authored-by: realbigsean <sean@sigmaprime.io>
Co-authored-by: antondlr <anton@delaruelle.net>
Woodpile37 pushed a commit to Woodpile37/lighthouse that referenced this issue Jan 6, 2024
## Issue Addressed

We're OOM'ing on Docker builds on the Deneb branch sigp#3929

Are we ok to self host automated docker builds?


Co-authored-by: realbigsean <seananderson33@gmail.com>
Co-authored-by: realbigsean <sean@sigmaprime.io>
Co-authored-by: antondlr <anton@delaruelle.net>
Woodpile37 pushed a commit to Woodpile37/lighthouse that referenced this issue Jan 6, 2024
## Issue Addressed

We're OOM'ing on Docker builds on the Deneb branch sigp#3929

Are we ok to self host automated docker builds?


Co-authored-by: realbigsean <seananderson33@gmail.com>
Co-authored-by: realbigsean <sean@sigmaprime.io>
Co-authored-by: antondlr <anton@delaruelle.net>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants