馃悰 Bug description
When running plugin with default settings (with dockerless = false) it uses docker image to run cargo and rustc (contradictive decision, but OK), and then it creates a lot of files (mostly in ./target directory and in ~/.cargo) which are not accessible for my user. Because the owner is root!
馃 Expected Behavior
I would expect for docker images to not create files owned by root, but by my current user. And also probably dockerless by default should be enabled - I see no reason why I would choose to run docker to run compiler.
馃憻 Steps to reproduce
Just follow README - https://github.com/softprops/serverless-aws-rust#-how-to-be-a-wizard
馃實 Your environment
serverless version: 1.74.1
rust-plugin version: 0.3.8
馃悰 Bug description
When running plugin with default settings (with dockerless = false) it uses docker image to run cargo and rustc (contradictive decision, but OK), and then it creates a lot of files (mostly in ./target directory and in ~/.cargo) which are not accessible for my user. Because the owner is root!
馃 Expected Behavior
I would expect for docker images to not create files owned by root, but by my current user. And also probably dockerless by default should be enabled - I see no reason why I would choose to run docker to run compiler.
馃憻 Steps to reproduce
Just follow README - https://github.com/softprops/serverless-aws-rust#-how-to-be-a-wizard
馃實 Your environment
serverless version: 1.74.1
rust-plugin version: 0.3.8