Thanks for your response @alan . I used "docker-compose up" to start Postgres/Redis and here's what I got from the logs. Still not able to start the server

It doesn't sound like Postgres initializes appropriately. I would probably try "docker-compose down" to remove everything and then rerun the "docker-compose up." Note: This will also delete any data stored in the PostgreSQL database. If all else fails, you can create the database requirements manually. The details are in the directory file README.md, located in ~/medium/packages/server The README.md has.

looks like the problem isn't from the initialization. I just compared the logs to what's here: https://www.medplum.com/docs/contributing/run-the-stack and it's the exact same result I should get.

You'll need a semicolon at the end to terminates a SQL command. 😉

❯ docker exec -it medplum-postgres-1 psql -U medplum
psql (12.15 (Debian 12.15-1.pgdg110+1))
Type "help" for help.

medplum=# SELECT rolname FROM pg_roles;
          rolname
---------------------------
 pg_monitor
 pg_read_all_settings
 pg_read_all_stats
 pg_stat_scan_tables
 pg_read_server_files
 pg_write_server_files
 pg_execute_server_program
 pg_signal_backend
 medplum
(9 rows)

Thanks for the help @alan , I was able to fix this with the help of Cody. The issue was that I had postgres running on my machine, so medplum/server by default was trying to use that instead of the docker postgres. I had to first terminate the postgres service on my machine before I could get this to run with docker

Good deal! I'm surprised there wasn't an error about port 5432 already in use when docker started if another instances was already running.