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
> 💡 The -v (volume mount) flags for `/root/.cargo/{registry,git}` are optional but when supplied, provides a much faster turn around when doing iterative development
50
+
> 💡 The -v (volume mount) flags for `/cargo/{registry,git}` are optional but when supplied, provides a much faster turn around when doing iterative development
51
+
52
+
Note that `-u $(id -u):$(id -g)` argument is crucial for the container to produce artifacts
53
+
owned by the current host user, otherwise you won't be able to `rm -rf target/lambda`
54
+
or run `cargo update`, because the container will write artifacts owned by `root` docker user
55
+
to `target/lambda` and `./cargo/{registry,git}` dirs which will break your dev and/or ci environment.
56
+
57
+
You should also ensure that you do have `${HOME}/.cargo/{registry,git}` dirs created
58
+
on your host machine, otherwise docker will create them automatically and assign `root` user
59
+
as an owner for these dirs which is unfortunate...
50
60
51
61
If you are using Windows, the command above may need to be modified to include
52
62
a `BIN` environment variable set to the name of the binary to be build and packaged
0 commit comments