a year ago
13 3.267 cargo:rerun-if-env-changed=PKG_CONFIG
13 3.267 cargo:rerun-if-env-changed=PKGCONFIGSYSROOTDIRx86_64-unknown-linux-musl
13 3.267 cargo:rerun-if-env-changed=PKGCONFIGSYSROOTDIRx8664unknownlinuxmusl
13 3.267 cargo:rerun-if-env-changed=TARGETPKGCONFIGSYSROOTDIR
13 3.267 cargo:rerun-if-env-changed=PKGCONFIGSYSROOT_DIR
13 3.267 run pkg_config fail: pkg-config has not been configured to support cross-compilation.
13 3.267
13 3.267 Install a sysroot for the target platform and configure it via
13 3.267 PKGCONFIGSYSROOTDIR and PKGCONFIG_PATH, or install a
13 3.267 cross-compiling wrapper for pkg-config and set it via
13 3.267 PKG_CONFIG environment variable.
13 3.267
13 3.267 --- stderr
13 3.267 thread 'main' panicked at /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/openssl-sys-0.9.102/build/find_normal.rs:190:5:
13 3.267
13 3.267
13 3.267 Could not find directory of OpenSSL installation, and this -sys
crate cannot
13 3.267 proceed without this knowledge. If OpenSSL is installed and this crate had
13 3.267 trouble finding it, you can set the OPENSSL_DIR
environment variable for the
13 3.267 compilation process.
13 3.267
13 3.267 Make sure you also have the development packages of openssl installed.
13 3.267 For example, libssl-dev
on Ubuntu or openssl-devel
on Fedora.
13 3.267
13 3.267 If you're in a situation where you think the directory should be found
13 3.267 automatically, please open a bug at https://github.com/sfackler/rust-openssl
13 3.267 and include information about your system as well as this message.
13 3.267
13 3.267 $HOST = x86_64-unknown-linux-gnu
13 3.267 $TARGET = x86_64-unknown-linux-musl
13 3.267 openssl-sys = 0.9.102
13 3.267
13 3.267
13 3.267 note: run with RUST_BACKTRACE=1
environment variable to display a backtrace
13 3.267 warning: build failed, waiting for other jobs to finish…
13 ERROR: process "/bin/bash -ol pipefail -c cargo build --release --target x86_64-unknown-linux-musl" did not complete successfully: exit code: 101
[stage-0 7/8] RUN --mount=type=cache,id=s/9dd03135-c784-475c-b2b2-ba9c27234400-/root/cargo/git,target=/root/.cargo/git --mount=type=cache,id=s/9dd03135-c784-475c-b2b2-ba9c27234400-/root/cargo/registry,target=/root/.cargo/registry --mount=type=cache,id=s/9dd03135-c784-475c-b2b2-ba9c27234400-target,target=/app/target cargo build --release --target x86_64-unknown-linux-musl:
3.267 automatically, please open a bug at https://github.com/sfackler/rust-openssl
3.267 and include information about your system as well as this message.
3.267
3.267 $HOST = x86_64-unknown-linux-gnu
3.267 $TARGET = x86_64-unknown-linux-musl
3.267 openssl-sys = 0.9.102
3.267
3.267
3.267 note: run with RUST_BACKTRACE=1
environment variable to display a backtrace
3.267 warning: build failed, waiting for other jobs to finish…
Dockerfile:20
18 | COPY . /app/.
19 | RUN --mount=type=cache,id=s/9dd03135-c784-475c-b2b2-ba9c27234400-/root/cargo/git,target=/root/.cargo/git --mount=type=cache,id=s/9dd03135-c784-475c-b2b2-ba9c27234400-/root/cargo/registry,target=/root/.cargo/registry --mount=type=cache,id=s/9dd03135-c784-475c-b2b2-ba9c27234400-target,target=/app/target mkdir -p bin
20 | >>> RUN --mount=type=cache,id=s/9dd03135-c784-475c-b2b2-ba9c27234400-/root/cargo/git,target=/root/.cargo/git --mount=type=cache,id=s/9dd03135-c784-475c-b2b2-ba9c27234400-/root/cargo/registry,target=/root/.cargo/registry --mount=type=cache,id=s/9dd03135-c784-475c-b2b2-ba9c27234400-target,target=/app/target cargo build --release --target x86_64-unknown-linux-musl
21 | RUN --mount=type=cache,id=s/9dd03135-c784-475c-b2b2-ba9c27234400-/root/cargo/git,target=/root/.cargo/git --mount=type=cache,id=s/9dd03135-c784-475c-b2b2-ba9c27234400-/root/cargo/registry,target=/root/.cargo/registry --mount=type=cache,id=s/9dd03135-c784-475c-b2b2-ba9c27234400-target,target=/app/target cp target/x86_64-unknown-linux-musl/release/yugioh-api-server bin
22 |
ERROR: failed to solve: process "/bin/bash -ol pipefail -c cargo build --release --target x86_64-unknown-linux-musl" did not complete successfully: exit code: 101
Error: Docker build failed
ⓘ Deployment information is only viewable by project members and Railway employees.
0 Replies