Every time we start ElixirDrip, it will try to connect to a running Postgres database. If we run it in our local development environment inside a container, it will be no different. In this case, we may install Postgres locally, we can set the application to connect to a remote database provided as a service, or we can spin up a new container running a Postgres database. Since this is only for local development purposes, the container option suits us well. Because we don't care about the data that we'll temporarily store, it can be deleted as soon as the container stops.
The next steps now could be writing the Dockerfile for the database container and then creating the Docker network plumbing to connect ...