we've had a single code location using the DockerR...
# ask-community
d
we've had a single code location using the DockerRunLauncher and having the configuration pass in the code directory as a volume mount via the
run_launcher
section of
dagster.yaml
. I'm now realizing that we can't do that if we want additional code locations, as it would just use the original code location's codebase every time. We're using gRPC code containers as our locations. Is the only option to have multiple code locations using gRPC containers to bake the code into the container image via the dockerfile? I would prefer to avoid rebuilding the image every time we need to make code changes.