Issue building Docker image when using a Rust Workspace project and Trunk

[jsoneaday]

My project has multiple sub projects inside of it. One of them, web, is built using trunk. The issue I'm having is that when I call trunk build inside the web project it creates files it is using on the root of the workspace under target. Unfortunately once I declare a WORKDIR for docker on the web project folder it is no longer able "to see" into its parent workspace's target folder.
Is there any way around this? Here's the error and some related items.

Error during Docker build

101.4 2024-02-11T22:38:17.466542Z  INFO installing wasm-bindgen
101.5 2024-02-11T22:38:17.584484Z  INFO calling wasm-bindgen for rustyindie-web
101.5 2024-02-11T22:38:17.587681Z ERROR error
101.5 error from build pipeline
101.5 
101.5 Caused by:
101.5     0: HTML build pipeline failed (1 errors), showing first
101.5     1: error from asset pipeline
101.5     2: wasm-bindgen not found
101.5     3: error running wasm-bindgen using executable '/root/.cache/trunk/wasm-bindgen-0.2.89/wasm-bindgen' with args: '["--target=web", "--out-dir=/usr/src/rustyindie-web/target/wasm-bindgen/release", "--out-name=rustyindie-web-bb804058ded840db", "/usr/src/rustyindie-web/target/wasm32-unknown-unknown/release/rustyindie-web.wasm", "--no-typescript"]'
101.5     4: No such file or directory (os error 2)
101.5 Error: error from build pipeline

Dockerfile

FROM rustlang/rust:nightly-alpine as builder
WORKDIR /usr/src/rustyindie-web
COPY . .
RUN apk add musl-dev
RUN rustup target add wasm32-unknown-unknown
RUN cargo install wasm-bindgen-cli
RUN cargo install trunk
# first setup web build
WORKDIR /usr/src/rustyindie-web/web
RUN cargo install wasm-bindgen-cli
RUN cargo install trunk
RUN trunk build --release

Project Structure

[ctron]

Not sure what the issue is, it would be good to have a reproducer for this. Wasm-bindgen needs to be of the same version as used in the web project. So installing one with cargo, without specifying that exact version of your web project won't help. Trunk will then try to install it's own version, which might not work in docker depending on some factors. I am not sure what it thinks it found a version, but then is not able to find it when executing it.

There's also the --offline option, which might make sense in a docker setup, because it will fail over a missing too, rather than downloading a random version during the build (in a container).

Also, it might be useful (faster) to use cargo binstall, fetching a binary version of trunk, rather than compiling trunk over and over again.

My expectation would be that installing wasm-bindgen and trunk once should be enough. Unless there's something weird going on.

Also, I would not recommend to use nightly, that's only a source of trouble. Unless you're really up for it.