> [!META]- Inline Metadata > [status:: boat] > [source:: https://vsupalov.com/rebuilding-docker-image-development/] > [tags:: #note/evergreen #state/boat #concepts/containerization/docker ] > [up:: [[Docker MOC]]] When using `docker run`, the `--mount` parameter allows you to specify a directory to recreate within the Docker container so that you can edit your code locally and then run it within the Docker container without rebuilding the image. > [!NOTE] > Consider whether coding [[Remote Development with VS Code#Developing with Docker|within a running container]] fits your use case better. ## Example `docker run -it --mount type=bind,source="$(pwd)/tests",target=/tests image_tag` This uses the `tests` directory within the working directory as the source and puts the contents within a directory `/tests` in the container whenever you call `docker run`. ## Source [You Don't Need to Rebuild Your Development Docker Image on Every Code Change](https://vsupalov.com/rebuilding-docker-image-development/) [Bind mounts - Docker documentation](https://docs.docker.com/storage/bind-mounts/)