Allow writing Cargo.toml in project directory.

README.md

@@ -278,10 +278,6 @@ $ QEMU_STRACE=1 cross run --target aarch64-unknown-linux-gnu
   work because `cross` use docker containers only mounts the Cargo project so
   the container doesn't have access to the rest of the filesystem.
 
-- `cross` will mount the Cargo project as READ ONLY. Thus, if any crate attempts
-  to modify its “source”, the build will fail. Well behaved crates should only
-  ever write to `$OUT_DIR` and never modify `$CARGO_MANIFEST_DIR` though.
-
 ## License
 
 Licensed under either of

src/docker.rs

@@ -98,15 +98,6 @@ pub fn run(target: &Target,
     };
     cmd.args(args);
 
-    // We create/regenerate the lockfile on the host system because the Docker
-    // container doesn't have write access to the root of the Cargo project
-    let cargo_toml = root.join("Cargo.toml");
-    Command::new("cargo").args(&["fetch",
-                "--manifest-path",
-                &cargo_toml.display().to_string()])
-        .run(verbose)
-        .chain_err(|| "couldn't generate Cargo.lock")?;
-
     let mut docker = docker_command("run");
 
     docker
@@ -155,7 +146,7 @@ pub fn run(target: &Target,
         .args(&["-v", &format!("{}:/xargo:Z", xargo_dir.display())])
         .args(&["-v", &format!("{}:/cargo:Z", cargo_dir.display())])
         .args(&["-v", "/cargo/bin"]) // Prevent `bin` from being mounted inside the Docker container.
-        .args(&["-v", &format!("{}:/project:Z,ro", root.display())])
+        .args(&["-v", &format!("{}:/project:Z", root.display())])
         .args(&["-v", &format!("{}:/rust:Z,ro", sysroot.display())])
         .args(&["-v", &format!("{}:/target:Z", target_dir.display())])
         .args(&["-w", "/project"]);