Closed roman-kashitsyn closed 1 year ago
Have you tried https://github.com/dfinity/sdk/pull/3303? Might fix this issue. But it was only merged a couple days ago, so you need to build a dfx yourself.
Have you tried #3303? Might fix this issue. But it was only merged a couple days ago, so you need to build a dfx yourself.
Right, I used the latest official version. I'll wait for the next release then. Thanks!
Description
I have a canister that I build with Bazel:
(see https://sourcegraph.com/github.com/dfinity/ic@736c901206ff5b6b06b251f99861c8a78ad58d4e/-/blob/rs/ethereum/cketh/testnet/dfx.json)
The first time I deploy my canisters, everything works fine. But if I modify the canister source and run
dfx deploy
again, the deploy fails because the canister module in.dfx/local
is read-only.The most likely cause is that Bazel marks all build artifacts as read-only:
and DFX copies custom Wasm files without changing the destination attributes:
https://sourcegraph.com/github.com/dfinity/sdk@412ed4702689820d61b1c11d5b3e444d1416a51d/-/blob/src/dfx-core/src/fs/mod.rs?L18:8-18:12
I expected to see this happen:
dfx deploy
works every time even if the source Wasm module is read-only.Instead, this happened:
dfx deploy
fails with the following error:Workarounds
Removing the .dfx destination file and re-running
dfx deploy
works.Meta
dfx --version
: