-
Notifications
You must be signed in to change notification settings - Fork 517
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
Unable to run the substrate dockerfile #2750
Comments
Yeah the Dockerfile was probably not updated for the new repo structure. Maybe you could fix it @kamalbuilds and add a pr? |
@bkchr I dont know how to fix it coz I have been struggliug to make the node run from past 3 days. Fixed the earlier to arrive at this . |
Had a look but Once I fix up the dirs I get: |
i've been going through fixing this too since yesterday since i want to use the Substrate Docker for a hackathon where the audience could be using different operating systems. i'm using a macOS M2 Pro 64Gb and it takes ~52 mins to build. so far i've fixed the following errors:
but i still got the following error because the latest docker.io/paritytech/ci-linux:production hasn't been updated for 10 months and is still using
so since i can't modify that docker.io/paritytech/ci-linux:production without first creating a separate PR to https://github.com/paritytech/scripts/blob/master/dockerfiles/ci-linux/Dockerfile, so in the interim i'm modifying the line so just to clarify, if i get it to work, and we want to update docker.io/paritytech/ci-linux:production to use the latest Rust version that is compatible with the polkadot-sdk rather than the old version note: docker.io/paritytech/ci-linux:production uses code from these repos:
the above errors seem to be the reason why other issues like this #2301 are being created. FYI, for my own project for xcm testing i created a custom version of docker.io/paritytech/ci-linux:production that uses a more recent Rust version here https://github.com/ltfschoen/XCMTemplate/blob/main/docker/Dockerfile |
Is there an existing issue?
Experiencing problems? Have you tried our Stack Exchange first?
Description of bug
=> ERROR [builder 4/4] RUN cargo build --locked --release 2.7s
substrate_builder.Dockerfile:6
4 | WORKDIR /substrate
5 | COPY . /substrate
6 | >>> RUN cargo build --locked --release
7 |
8 | # This is the 2nd stage: a very small image where we copy the Substrate binary."
ERROR: failed to solve: process "/bin/sh -c cargo build --locked --release" did not complete successfully: exit code: 101
Steps to reproduce
cd substrate/docker
./build.sh
The text was updated successfully, but these errors were encountered: