Why does 'surrealdb' fail during cargo build?

[callmeitachi]

this is my Dockerfile:
FROM rust:latest
WORKDIR /app/
COPY Cargo.toml ./
COPY src ./src
RUN cargo build --release
CMD ["./target/release/nono"]

warning: [email protected]: Compiler family detection failed due to error: ToolExecError: command did not execute successfully (status code signal: 11 (SIGSEGV) (core dumped)): "cc" "-E" "/app/target/release/build/ring-ce7012920b9876b5/out/9664684946312223368detect_compiler_family.c"
warning: [email protected]: cc: internal compiler error: Segmentation fault signal terminated program cc1
warning: [email protected]: Please submit a full bug report, with preprocessed source (by using -freport-bug).
warning: [email protected]: See file:///usr/share/doc/gcc-12/README.Bugs for instructions.
error: failed to run custom build command for ring v0.17.14

Caused by:
process didn't exit successfully: /app/target/release/build/ring-52344adb28f1b33c/build-script-build (exit status: 1)
--- stdout
cargo:rerun-if-env-changed=CARGO_MANIFEST_DIR
cargo:rerun-if-env-changed=CARGO_PKG_NAME
cargo:rerun-if-env-changed=CARGO_PKG_VERSION_MAJOR
cargo:rerun-if-env-changed=CARGO_PKG_VERSION_MINOR
cargo:rerun-if-env-changed=CARGO_PKG_VERSION_PATCH
cargo:rerun-if-env-changed=CARGO_PKG_VERSION_PRE
cargo:rerun-if-env-changed=CARGO_MANIFEST_LINKS
cargo:rerun-if-env-changed=RING_PREGENERATE_ASM
cargo:rerun-if-env-changed=OUT_DIR
cargo:rerun-if-env-changed=CARGO_CFG_TARGET_ARCH
cargo:rerun-if-env-changed=CARGO_CFG_TARGET_OS
cargo:rerun-if-env-changed=CARGO_CFG_TARGET_ENV
cargo:rerun-if-env-changed=CARGO_CFG_TARGET_ENDIAN
OPT_LEVEL = Some(3)
OUT_DIR = Some(/app/target/release/build/ring-ce7012920b9876b5/out)
TARGET = Some(x86_64-unknown-linux-gnu)
HOST = Some(x86_64-unknown-linux-gnu)
cargo:rerun-if-env-changed=CC_x86_64-unknown-linux-gnu
CC_x86_64-unknown-linux-gnu = None
cargo:rerun-if-env-changed=CC_x86_64_unknown_linux_gnu
CC_x86_64_unknown_linux_gnu = None
cargo:rerun-if-env-changed=HOST_CC
HOST_CC = None
cargo:rerun-if-env-changed=CC
CC = None
cargo:rerun-if-env-changed=CC_ENABLE_DEBUG_OUTPUT
cargo:warning=Compiler family detection failed due to error: ToolExecError: command did not execute successfully (status code signal: 11 (SIGSEGV) (core dumped)): "cc" "-E" "/app/target/release/build/ring-ce7012920b9876b5/out/9664684946312223368detect_compiler_family.c"
RUSTC_WRAPPER = None
cargo:rerun-if-env-changed=CRATE_CC_NO_DEFAULTS
CRATE_CC_NO_DEFAULTS = None
DEBUG = Some(false)
CARGO_CFG_TARGET_FEATURE = Some(fxsr,sse,sse2)
cargo:rerun-if-env-changed=CFLAGS
CFLAGS = None
cargo:rerun-if-env-changed=HOST_CFLAGS
HOST_CFLAGS = None
cargo:rerun-if-env-changed=CFLAGS_x86_64_unknown_linux_gnu
CFLAGS_x86_64_unknown_linux_gnu = None
cargo:rerun-if-env-changed=CFLAGS_x86_64-unknown-linux-gnu
CFLAGS_x86_64-unknown-linux-gnu = None
CARGO_ENCODED_RUSTFLAGS = Some()
cargo:warning=cc: internal compiler error: Segmentation fault signal terminated program cc1
cargo:warning=Please submit a full bug report, with preprocessed source (by using -freport-bug).
cargo:warning=See file:///usr/share/doc/gcc-12/README.Bugs for instructions.

--- stderr

error occurred in cc-rs: command did not execute successfully (status code exit status: 4): LC_ALL="C" "cc" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64" "-I" "/usr/local/cargo/registry/src/rsproxy.cn-0dccff568467c15b/ring-0.17.14/include" "-I" "/usr/local/cargo/registry/src/rsproxy.cn-0dccff568467c15b/ring-0.17.14/pregenerated" "-Wall" "-Wextra" "-fvisibility=hidden" "-std=c1x" "-Wall" "-Wbad-function-cast" "-Wcast-align" "-Wcast-qual" "-Wconversion" "-Wmissing-field-initializers" "-Wmissing-include-dirs" "-Wnested-externs" "-Wredundant-decls" "-Wshadow" "-Wsign-compare" "-Wsign-conversion" "-Wstrict-prototypes" "-Wundef" "-Wuninitialized" "-g3" "-DNDEBUG" "-o" "/app/target/release/build/ring-ce7012920b9876b5/out/a4019cc0736b0423-crypto.o" "-c" "/usr/local/cargo/registry/src/rsproxy.cn-0dccff568467c15b/ring-0.17.14/crypto/crypto.c"

warning: build failed, waiting for other jobs to finish...

[Rushmore75]

Looks like your building in docker - does it build find locally?