cp ./target/release/$APP_NAME /bin/server
EOF
################################################################################
# Create a new stage for running the application that contains the minimal
# runtime dependencies for the application. This often uses a different base
# image from the build stage where the necessary files are copied from the build
# stage.
#
# The example below uses the debian bullseye image as the foundation for running the app.
# By specifying the "bullseye-slim" tag, it will also use whatever happens to be the
# most recent version of that tag when you build your Dockerfile. If
# reproducibility is important, consider using a digest
# (e.g., debian@sha256:ac707220fbd7b67fc19b112cee8170b41a9e97f703f588b2cdbbcdcecdd8af57).
FROM debian:bullseye-slim AS final
# Create a non-privileged user that the app will run under.
# See https://docs.docker.com/develop/develop-images/dockerfile_best-practices/ #user
ARG UID=10001
RUN adduser \
--disabled-password \
--gecos "" \
--home "/nonexistent" \
--shell "/sbin/nologin" \
--no-create-home \
--uid "${UID}" \
appuser
USER appuser
# Copy the executable from the "build" stage.
COPY --from=build /bin/server /bin/
# Expose the port that the application listens on.
EXPOSE 8000
# What the container should run when it is started.
CMD ["/bin/server"]
```
4. In the cloned repository's directory, run `docker build` to build the image.
```console
$ docker build -t rust-backend-image .
```
5. Run `docker run` with the following options to run the image as a container on the same network as the database.
```console
$ docker run \
--rm -d \
--network postgresnet \
--name docker-develop-rust-container \
-p 3001:8000 \
-e PG_DBNAME=example \
-e PG_HOST=db \
-e PG_USER=postgres \
-e PG_PASSWORD=mysecretpassword \
-e ADDRESS=0.0.0.0:8000 \
-e RUST_LOG=debug \
rust-backend-image
```
6. Curl the application to verify that it connects to the database.
```console
$ curl http://localhost:3001/users
```
You should get a response like the following.
```json
[{ "id": 1, "login": "root" }]
```
## Use Compose to develop locally
When you run `docker init`, in addition to a `Dockerfile`, it also creates a `compose.yaml` file.
This Compose file is super convenient as you don't have to type all the parameters to pass to the `docker run` command. You can declaratively do that using a Compose file.
In the cloned repository's directory, open the `compose.yaml` file in an IDE or text editor. `docker init` handled creating most of the instructions, but you'll need to update it for your unique application.
You need to update the following items in the `compose.yaml` file:
- Uncomment all of the database instructions.
- Add the environment variables under the server service.
The following is the updated `compose.yaml` file.
```yaml {hl_lines=["17-23","30-55"]}
# Comments are provided throughout this file to help you get started.
# If you need more help, visit the Docker compose reference guide at
# https://docs.docker.com/reference/compose-file/
# Here the instructions define your application as a service called "server".