Gitlab loses all information

I can bring up gitlab by running docker-compose up using the default yml file, and can configure gitlab with projects/users, etc..., but when I bring down gitlab (restart machine), then bring back up using docker-compose up, it seems as though all my previous configuration is gone. Is there something within the yml file I need to change? Below is output:

PS D:> docker-compose up
Starting default_redis_1
Starting default_postgresql_1
Starting default_gitlab_1
Attaching to default_postgresql_1, default_redis_1, default_gitlab_1
postgresql_1 | Initializing datadir...
redis_1 | Starting redis-server...
redis_1 | [1] 15 Apr 14:21:26.863 # Server started, Redis version 2.8.4
postgresql_1 | Initializing certdir...
postgresql_1 | Initializing logdir...
postgresql_1 | Initializing rundir...
postgresql_1 | Setting resolv.conf ACLs...
gitlab_1 | Initializing logdir...
gitlab_1 | Initializing datadir...
gitlab_1 | Installing configuration templates...
gitlab_1 | Configuring gitlab...
postgresql_1 | Creating database user: gitlab
postgresql_1 | Creating database: gitlabhq_production...
postgresql_1 | ΓÇú Loading pg_trgm extension...
postgresql_1 | ΓÇú Granting access to gitlab user...
postgresql_1 | Starting PostgreSQL 9.6...
postgresql_1 | LOG: database system was shut down at 2017-04-15 14:21:29 UTC
postgresql_1 | LOG: MultiXact member wraparound protections are now enabled
postgresql_1 | LOG: database system is ready to accept connections
postgresql_1 | LOG: autovacuum launcher started
gitlab_1 | Configuring gitlab::database...
gitlab_1 | Configuring gitlab::redis
gitlab_1 | Configuring gitlab::secrets...
gitlab_1 | Configuring gitlab::sidekiq...
gitlab_1 | Configuring gitlab::gitlab-workhorse...
gitlab_1 | Configuring gitlab::unicorn...
gitlab_1 | Configuring gitlab::timezone...
gitlab_1 | Configuring gitlab::rack_attack...
gitlab_1 | Configuring gitlab::ci...
gitlab_1 | Configuring gitlab::artifacts...
gitlab_1 | Configuring gitlab::lfs...
gitlab_1 | Configuring gitlab::mattermost...
gitlab_1 | Configuring gitlab::project_features...
gitlab_1 | Configuring gitlab::oauth...
gitlab_1 | Configuring gitlab::ldap...
gitlab_1 | Configuring gitlab::backups...
gitlab_1 | Configuring gitlab::backups::schedule...
gitlab_1 | Configuring gitlab::registry...
gitlab_1 | Configuring gitlab::pages...
gitlab_1 | Configuring gitlab-shell...
gitlab_1 | Configuring nginx...
gitlab_1 | Configuring nginx::gitlab...
gitlab_1 | 2017-04-15 19:51:32,522 CRIT Supervisor running as root (no user in config file)
gitlab_1 | 2017-04-15 19:51:32,522 WARN Included extra file "/etc/supervisor/conf.d/sidekiq.conf" during parsing
gitlab_1 | 2017-04-15 19:51:32,522 WARN Included extra file "/etc/supervisor/conf.d/mail_room.conf" during parsing
gitlab_1 | 2017-04-15 19:51:32,522 WARN Included extra file "/etc/supervisor/conf.d/gitlab-workhorse.conf" during p
arsing
gitlab_1 | 2017-04-15 19:51:32,522 WARN Included extra file "/etc/supervisor/conf.d/cron.conf" during parsing
gitlab_1 | 2017-04-15 19:51:32,522 WARN Included extra file "/etc/supervisor/conf.d/nginx.conf" during parsing
gitlab_1 | 2017-04-15 19:51:32,522 WARN Included extra file "/etc/supervisor/conf.d/unicorn.conf" during parsing
gitlab_1 | 2017-04-15 19:51:32,522 WARN Included extra file "/etc/supervisor/conf.d/sshd.conf" during parsing
gitlab_1 | 2017-04-15 19:51:32,562 INFO RPC interface 'supervisor' initialized
gitlab_1 | 2017-04-15 19:51:32,562 CRIT Server 'unix_http_server' running without any HTTP authentication checking
gitlab_1 | 2017-04-15 19:51:32,563 INFO supervisord started with pid 1
gitlab_1 | 2017-04-15 19:51:33,566 INFO spawned: 'sidekiq' with pid 499
gitlab_1 | 2017-04-15 19:51:33,569 INFO spawned: 'unicorn' with pid 500
gitlab_1 | 2017-04-15 19:51:33,573 INFO spawned: 'gitlab-workhorse' with pid 501
gitlab_1 | 2017-04-15 19:51:33,575 INFO spawned: 'cron' with pid 502
gitlab_1 | 2017-04-15 19:51:33,578 INFO spawned: 'nginx' with pid 503
gitlab_1 | 2017-04-15 19:51:33,581 INFO spawned: 'sshd' with pid 505
gitlab_1 | 2017-04-15 19:51:35,340 INFO success: sidekiq entered RUNNING state, process has stayed up for > than 1
seconds (startsecs)
gitlab_1 | 2017-04-15 19:51:35,340 INFO success: unicorn entered RUNNING state, process has stayed up for > than 1
seconds (startsecs)
gitlab_1 | 2017-04-15 19:51:35,340 INFO success: gitlab-workhorse entered RUNNING state, process has stayed up for

than 1 seconds (startsecs)
gitlab_1 | 2017-04-15 19:51:35,340 INFO success: cron entered RUNNING state, process has stayed up for > than 1 sec
onds (startsecs)
gitlab_1 | 2017-04-15 19:51:35,340 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 se
conds (startsecs)
gitlab_1 | 2017-04-15 19:51:35,340 INFO success: sshd entered RUNNING state, process has stayed up for > than 1 sec
onds (startsecs)
gitlab_1 | 2017-04-15 19:51:43,099 INFO exited: unicorn (exit status 1; not expected)
gitlab_1 | 2017-04-15 19:51:44,101 INFO spawned: 'unicorn' with pid 521
gitlab_1 | 2017-04-15 19:51:45,412 INFO success: unicorn entered RUNNING state, process has stayed up for > than 1
seconds (startsecs)

Start with the default yml file and the docker-compose up workflow described in the report, then trace how GitLab, PostgreSQL, and Redis data are configured across a restart. Done means identifying why projects and users disappear and documenting or correcting the configuration so the data remains after bringing the services down and back up.