Docker build error returned a non-zero code: 101

Open
#6 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
docker, rust

Research direction

Start by reproducing the Docker build entry point that runs cargo build, then inspect the reported crossbeam-utils-0.5.0/src/cache_padded.rs failure and the project’s Rust dependency or toolchain configuration. Done means the grin-bot-node service image builds without the non-zero code 101 error.

Written by the indexing model from the issue text.

Description

.........
Compiling crossbeam-utils v0.5.0
error: the struct #[repr(align(u16))] attribute is experimental (see issue #33626)
--> /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/crossbeam-utils-0.5.0/src/cache_padded.rs:19:1
|
19 | #[repr(align(64))]
| ^^^^^^^^^^^^^^^^^^
error: non-string literals in attributes, or string literals in top-level positions, are experimental (see issue #34981)
--> /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/crossbeam-utils-0.5.0/src/cache_padded.rs:19:1
|
19 | #[repr(align(64))]
| ^^^^^^^^^^^^^^^^^^
error: aborting due to 2 previous errors
error: Could not compile crossbeam-utils.
warning: build failed, waiting for other jobs to finish...
error: build failed
ERROR: ### Service 'grin-bot-node' failed to build: The command '/bin/sh -c cargo build' returned a non-zero code: 101

Dominant language
JavaScript
Stars
11
Forks
10
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mimblewimble/grin-docker

All issues in mimblewimble/grin-docker

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.