Clarify what `chef` needs in the build context

[michaelbeaumont]

In the example Dockerfile we see multiple:

COPY . .

Can it be clarified what's actually needed by chef here? It doesn't seem to need target, for example, right?

Can we just put

COPY Cargo.toml Cargo.lock ./
COPY src ./src

in the example or otherwise include a minimal .dockerignore?

[0xangelo]

I also include the .cargo directory, since sometimes I have workspace-wide build configurations or custom registries set up. My .dockerignore ends up looking like this: https://github.com/0xangelo/cargo-workspace-template/blob/main/.dockerignore

[sergiomeneses]

please carify this, right now i have the following in my .dockerignore:

*

!.cargo
!src/
!Cargo.lock
!Cargo.toml

Also you must include in this list any folder/file you reference in your code

[failable]

Same question

[LukeMathWalker]

It needs all the source files that make up your package as well as any configuration that may alter the way a cargo command is executed (e.g. .cargo/config.toml).
There's no one size fits all here.