If I'm building an Erlang release inside docker, is there a way to avoid downloading (and recompiling?) the dependencies every time? Using rebar3.
I don't necessarily want to mount the local directory in the container, 'cos I might have compiled the deps locally, and I'm using a different Linux (Ubuntu locally, Alpine in the container).
@rogerlipscombe Can you do the fetch/build of dependencies as a separate layer? For example, this Elixir Dockerfile [https://github.com/mbta/tablespoon/blob/main/Dockerfile#L14-L18] copies only the files needed to fetch/build the dependencies, and then as another layer copies the application files and builds the release.
@paulswartz Yep. That seems to work. Thanks.
@rogerlipscombe #shamelessplug funny, but this 50% of the use-case warp.build is being built for.
the other 50% is incrementally running tests based on actual code-changes and not file modification dates.