Replies: 4 comments 1 reply
-
though i dont know if its relevant here i are my docker file and docker-compose:
docker-compose:
.env file:
if i add a .cargo/config.toml with the target anywhere outside my project workspace, it seems to work fine
But ofcourse that means anytime i restart/rebuild the container, i have to rebuild the project/binaries. which makes it not seem like a good solution |
Beta Was this translation helpful? Give feedback.
-
btw - is there an official place for vscode/devcontainer support/issues? |
Beta Was this translation helpful? Give feedback.
-
Hi 👋 The error message "Operation not permitted (os error 1)" suggests that the Rust compiler is unable to write to the target directory. This is likely due to a file system permission issue. Given that you're running your Rust project inside a Docker container on Windows, one possible cause of this issue is the file sharing settings of Docker Desktop. Docker Desktop needs permission to share files between your Windows file system and the Docker containers. Here are the steps to check and update your file sharing settings:
Let us know if this helps, else we can try digging more into the issue, thanks! |
Beta Was this translation helpful? Give feedback.
-
Thank you. i feel this may be on the track to what the issue is related to (especially considering my files are on a locally mapped google drive), but i do not find 'File Sharing' under the settings you mentioned. I am using WSL2, and do see from the docs here that this option is not available when using WSL2: https://docs.docker.com/desktop/synchronized-file-sharing/ |
Beta Was this translation helpful? Give feedback.
-
Problem
Im not sure if should be reaching out here or vscode for help on this...but i will start here and let me know if im int he wrong location..
i have built a vs code devcontainer based on
mcr.microsoft.com/devcontainers/rust:1-1-bullseye
, running under Docker Desktop on windows 11. I am able to run a basic example using this without any dependenciesi have the following structure (Note: the target and Cargo.lock do not exist until after i attempt a
cargo build
:My toml looks like this:
when i do
Cargo build
or run from command line, i see this:i checked these folders and they are all r/w.
What am i doing wrong?
Steps
cargo new test
cargo build
twiceVersion
rustc 1.78.0 (9b00956e5 2024-04-29)
cargo 1.78.0 (54d8815d0 2024-03-26)
vscode ➜ /workspaces/aipg_client $ cargo -vV
cargo 1.78.0 (54d8815d0 2024-03-26)
release: 1.78.0
commit-hash: 54d8815d04fa3816edc207bbc4dd36bf18014dbc
commit-date: 2024-03-26
host: x86_64-unknown-linux-gnu
libgit2: 1.7.2 (sys:0.18.2 vendored)
libcurl: 8.6.0-DEV (sys:0.4.72+curl-8.6.0 vendored ssl:OpenSSL/1.1.1w)
ssl: OpenSSL 1.1.1w 11 Sep 2023
os: Debian 11 (bullseye) [64-bit]
vscode ➜ /workspaces/aipg_client $ cat /etc/debian_version
11.9
docker desktop v4.29.0
Beta Was this translation helpful? Give feedback.
All reactions