Closed ackintosh closed 2 years ago
Oh, I wasn't aware of this. Do I understand correctly that we should do this for all our Dockerfile
s across the ecosystem?
@mxinden Yes, I think so. 💡
CI / Run find-node (pull_request) Jul 8 05:36:07.137527 INFO 4.6920s OTHER<< single[007] (bacac7) >> This is a
main()
function that does nothing, for caching dependencies.
Hmm... the log shows that the dummy main
function which is generated by Dockerfile remains in the release binary.
I think main.rs
s mtime timestamps is not updated, like https://github.com/rust-lang/cargo/issues/9598.
cargo install
ignores Cargo.lock by default. Now builds on this project are failing due to incompatibility ofenr v0.6.1
, which is a dependency ofdiscv5
. Note: Currently we are usingdiscv5
on master branch, not published on crates.io.In order to fix the build error, added
--locked
flag so thatcargo install
respects Cargo.lock.