You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Experiencing problems? Have you tried our Stack Exchange first?
This is not a support question.
Content request
following the tutorial on a windows machine with ubuntu using wsl can lead to directory mounting issues. (had it myself).
quick guide i created to fix the issues:
Errors like
cargo:warning=rocksdb/table/block_based/block_based_table_reader.cc:2943:1: fatal error: error writing to /tmp/ccFEjz7y.s: Read-only file system
cargo:warning= 2943 | } // namespace ROCKSDB_NAMESPACE
cargo:warning= | ^
cargo:warning=compilation terminated.
exit status: 1
indicate missing write permission on mounted /tmp directory. Since ubuntu is running as a wsl on windows the following steps need to be made.
check permissions with ls -ld /tmp
should be drwxrwxrwt ? ? ? ? Nov 20 08:35 /tmp
check permissions on mounted drive with mount
/dev/sdb on / type ext4 (ro,relatime,discard,errors=remount-ro,data=ordered) shows read-only (ro) mount for root folder. needs to be read-write (rw).
Update the mounted directory permission.
Change WSL Default Mount Options:
Open the WSL configuration file /etc/wsl.conf using a text editor within WSL (e.g., nano, vim, or gedit): sudo nano /etc/wsl.conf (If the file doesn't exist, you can create it.)
Add Mount Options:
Add the following lines to the wsl.conf file to specify the default mount options:
[wsl2]
options = "metadata"
Save the file and exit the text editor. (Ctrl + X, save file)
Restart WSL
Check the mounted directory permission. with mount.
e.g. /dev/sdb on / type ext4 (rw,relatime,discard,errors=remount-ro,data=ordered)
Following the tutorial can lead to rust compiler version issues since the parachain repository release v1.0.0 is only compatible with certain versions.
following error was generated when executing cargo build --release in the cloned polkadot repository
Compiling sc-executor-common v0.10.0-dev (https://github.com/paritytech/substrate?branch=polkadot-v1.0.0#2b76b44e)
error[E0658]: use of unstable library feature 'once_cell'
--> /home/rustdev/.cargo/git/checkouts/substrate-7e08433d4c370a21/2b76b44/client/executor/wasmtime/src/util.rs:147:6
|
147 | use std::sync::OnceLock;
| ^^^^^^^^^^^^^^^^^^^
|
= note: see issue #74465 rust-lang/rust#74465 for more information
...
when adding a rust-toolchain.toml file to the cloned repository directory with the following specifications
[toolchain]
channel = "nightly-2023-05-22" # Specify the desired Rust Nightly version
components = [ "rustfmt" ] # Include additional components if needed
targets = [ "wasm32-unknown-unknown" ] # Specify additional targets if needed
profile = "minimal" # Choose the desired profile
it works. it would be helpful if that step is specified. else you have to check the rustc version in the release notes on github.
I hope this small FAQ I made for myself would be helpful to others following the building relay chain and parachain tutorial.
Are you willing to help with this request?
Yes!
The text was updated successfully, but these errors were encountered:
Is there an existing issue?
Experiencing problems? Have you tried our Stack Exchange first?
Content request
following the tutorial on a windows machine with ubuntu using wsl can lead to directory mounting issues. (had it myself).
quick guide i created to fix the issues:
Errors like
cargo:warning=rocksdb/table/block_based/block_based_table_reader.cc:2943:1: fatal error: error writing to /tmp/ccFEjz7y.s: Read-only file system
cargo:warning= 2943 | } // namespace ROCKSDB_NAMESPACE
cargo:warning= | ^
cargo:warning=compilation terminated.
exit status: 1
indicate missing write permission on mounted /tmp directory. Since ubuntu is running as a wsl on windows the following steps need to be made.
check permissions with ls -ld /tmp
should be drwxrwxrwt ? ? ? ? Nov 20 08:35 /tmp
check permissions on mounted drive with mount
/dev/sdb on / type ext4 (ro,relatime,discard,errors=remount-ro,data=ordered) shows read-only (ro) mount for root folder. needs to be read-write (rw).
Update the mounted directory permission.
Change WSL Default Mount Options:
Open the WSL configuration file /etc/wsl.conf using a text editor within WSL (e.g., nano, vim, or gedit): sudo nano /etc/wsl.conf (If the file doesn't exist, you can create it.)
Add Mount Options:
Add the following lines to the wsl.conf file to specify the default mount options:
[wsl2]
options = "metadata"
Save the file and exit the text editor. (Ctrl + X, save file)
Restart WSL
Check the mounted directory permission. with mount.
e.g. /dev/sdb on / type ext4 (rw,relatime,discard,errors=remount-ro,data=ordered)
Following the tutorial can lead to rust compiler version issues since the parachain repository release v1.0.0 is only compatible with certain versions.
following error was generated when executing cargo build --release in the cloned polkadot repository
Compiling sc-executor-common v0.10.0-dev (https://github.com/paritytech/substrate?branch=polkadot-v1.0.0#2b76b44e)
error[E0658]: use of unstable library feature 'once_cell'
--> /home/rustdev/.cargo/git/checkouts/substrate-7e08433d4c370a21/2b76b44/client/executor/wasmtime/src/util.rs:147:6
|
147 | use std::sync::OnceLock;
| ^^^^^^^^^^^^^^^^^^^
|
= note: see issue #74465 rust-lang/rust#74465 for more information
...
when adding a rust-toolchain.toml file to the cloned repository directory with the following specifications
[toolchain]
channel = "nightly-2023-05-22" # Specify the desired Rust Nightly version
components = [ "rustfmt" ] # Include additional components if needed
targets = [ "wasm32-unknown-unknown" ] # Specify additional targets if needed
profile = "minimal" # Choose the desired profile
it works. it would be helpful if that step is specified. else you have to check the rustc version in the release notes on github.
I hope this small FAQ I made for myself would be helpful to others following the building relay chain and parachain tutorial.
Are you willing to help with this request?
Yes!
The text was updated successfully, but these errors were encountered: