Django服务器不会在Docker-Compose中启动

我正试图将一个Django项目移植到Docker-Compose进行部署。

我跟着各种教程在线，从我的理解，我的应用程序需要的唯一的服务是Django和Postgres。 这是我的docker-compose.yml文件：

db: image: postgres:latest ports: - "5432" environment: POSTGRES_PASSWORD: postgres POSTGRES_USER: postgres web: build: . ports: - "8000:8000" volumes: - .:/code links: - db command: python3 manage.py runserver 0.0.0.0:8000 

我已经在我的virtualenv本地testing了python命令，并且服务器启动了，但是当我在应用程序的副本所在的文件夹中运行“docker-compose up”时，我得到以下输出：

 Creating hpr_db_1 Creating hpr_web_1 Attaching to hpr_db_1, hpr_web_1 db_1 | The files belonging to this database system will be owned by user "postgres". db_1 | This user must also own the server process. db_1 | db_1 | The database cluster will be initialized with locale "en_US.utf8". db_1 | The default database encoding has accordingly been set to "UTF8". db_1 | The default text search configuration will be set to "english". db_1 | db_1 | Data page checksums are disabled. db_1 | db_1 | fixing permissions on existing directory /var/lib/postgresql/data ... ok db_1 | creating subdirectories ... ok db_1 | selecting default max_connections ... 100 db_1 | selecting default shared_buffers ... 128MB db_1 | selecting dynamic shared memory implementation ... posix db_1 | creating configuration files ... ok db_1 | creating template1 database in /var/lib/postgresql/data/base/1 ... ok db_1 | initializing pg_authid ... ok db_1 | initializing dependencies ... ok web_1 | /usr/local/lib/python3.4/importlib/_bootstrap.py:321: RemovedInDjango19Warning: django.utils.importlib will be removed in Django 1.9. web_1 | return f(*args, **kwds) web_1 | db_1 | creating system views ... ok db_1 | loading system objects' descriptions ... ok db_1 | creating collations ... ok db_1 | creating conversions ... ok db_1 | creating dictionaries ... ok db_1 | setting privileges on built-in objects ... ok db_1 | creating information schema ... ok db_1 | loading PL/pgSQL server-side language ... ok web_1 | /usr/local/lib/python3.4/importlib/_bootstrap.py:321: RemovedInDjango19Warning: django.utils.importlib will be removed in Django 1.9. web_1 | return f(*args, **kwds) web_1 | db_1 | vacuuming database template1 ... ok db_1 | copying template1 to template0 ... ok db_1 | copying template1 to postgres ... ok db_1 | syncing data to disk ... ok db_1 | db_1 | Success. You can now start the database server using: db_1 | db_1 | postgres -D /var/lib/postgresql/data db_1 | or db_1 | pg_ctl -D /var/lib/postgresql/data -l logfile start db_1 | db_1 | db_1 | WARNING: enabling "trust" authentication for local connections db_1 | You can change this by editing pg_hba.conf or using the option -A, or db_1 | --auth-local and --auth-host, the next time you run initdb. db_1 | waiting for server to start....LOG: database system was shut down at 2015-11-06 15:18:39 UTC db_1 | LOG: MultiXact member wraparound protections are now enabled db_1 | LOG: autovacuum launcher started db_1 | LOG: database system is ready to accept connections db_1 | done db_1 | server started db_1 | ALTER ROLE db_1 | db_1 | db_1 | /docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/* db_1 | db_1 | LOG: received fast shutdown request db_1 | LOG: aborting any active transactions db_1 | LOG: autovacuum launcher shutting down db_1 | waiting for server to shut down....LOG: shutting down db_1 | LOG: database system is shut down db_1 | done db_1 | server stopped db_1 | db_1 | PostgreSQL init process complete; ready for start up. db_1 | db_1 | LOG: database system was shut down at 2015-11-06 15:18:41 UTC db_1 | LOG: MultiXact member wraparound protections are now enabled db_1 | LOG: database system is ready to accept connections db_1 | LOG: autovacuum launcher started 

没有消息关于服务器启动或类似的东西，我知道它编译我的代码由于有关弃用的警告消息，但我很难过这里。 任何人都能看到我的错误？

更新：

仔细检查并更改了DJango服务器的端口后，我发现访问网页的时候返回了一个“连接到服务器被重置，而页面被加载”的错误。 这表示正在设置该页面上的内容。 但我仍然无法访问它。 我知道Docker-Compose正在像教程中简单的Django应用程序一样工作。

Answer 1

你有没有显示django容器的端口？

Answer 2

使用.yml文件创build一个构build。

您应该将文件移动到部署环境并继续运行服务器。

因此，当.yml成功运行时，您将获得成功构build，并且您将能够将文件移动到部署环境（您有最后一个构build运行的地方）。

无论如何，我不build议在runner中执行python3 manage.py runserver 0.0.0.0:8000 ，因为你的runner将会运行，并且不会完成（获得成功或失败的构build）。