feat(docker-build): pass additional workspace directory

[prajwolrg]

Currently, docker only mounts the guest program workspace. However, mounting a different workspace can be useful. This PR allows passing an additional workspace_directory as BuildArgs.

[nhtyy]

Thank you for your patience on this PR!

Happy to take this over, but I think it be suitable to instead override the program dir? Therefore leading to a different workspace metadata?

See here:

sp1/crates/build/src/build.rs

Lines 30 to 43 in f9640e8

	let program_dir = program_dir
	.unwrap_or_else(|| std::env::current_dir().expect("Failed to get current directory."));
	let program_dir: Utf8PathBuf =
	program_dir.try_into().expect("Failed to convert PathBuf to Utf8PathBuf");
	// Get the program metadata.
	let program_metadata_file = program_dir.join("Cargo.toml");
	let mut program_metadata_cmd = cargo_metadata::MetadataCommand::new();
	let program_metadata = program_metadata_cmd.manifest_path(program_metadata_file).exec()?;
	// Get the command corresponding to Docker or local build.
	let cmd = if args.docker {
	create_docker_command(args, &program_dir, &program_metadata)?
	} else {

Currently, this is not exposed as an option via the CLI? Also likely this crate gets cleaned up more in the future so will keep this in mind going forward.

[prajwolrg]

Thank you for your patience on this PR!

Happy to take this over, but I think it be suitable to instead override the program dir? Therefore leading to a different workspace metadata?

See here:

sp1/crates/build/src/build.rs

Lines 30 to 43 in f9640e8

	let program_dir = program_dir
	.unwrap_or_else(|| std::env::current_dir().expect("Failed to get current directory."));
	let program_dir: Utf8PathBuf =
	program_dir.try_into().expect("Failed to convert PathBuf to Utf8PathBuf");
	// Get the program metadata.
	let program_metadata_file = program_dir.join("Cargo.toml");
	let mut program_metadata_cmd = cargo_metadata::MetadataCommand::new();
	let program_metadata = program_metadata_cmd.manifest_path(program_metadata_file).exec()?;
	// Get the command corresponding to Docker or local build.
	let cmd = if args.docker {
	create_docker_command(args, &program_dir, &program_metadata)?
	} else {

Currently, this is not exposed as an option via the CLI? Also likely this crate gets cleaned up more in the future so will keep this in mind going forward.

In our usecase, we had multiple guest programs in a single workspace. So, we used this approach. We didn't find it exposed via CLI. There seems to have been significant update on build from the last time I looked into this. Happy to help you and review for our usecase if you take it over.