为什么我无法通过"docker-compose run web"命令运行django迁移? [英] Why am I unable to run django migrations via the 'docker-compose run web' command?
问题描述
所以我正在通过docker-compose部署django，postgress和nginx容器，但有一个我似乎无法弄清的问题.
为了解决Django应用中的以下错误，我知道我只需要运行Django迁移即可.
docker@postgres ERROR: relation "accounts_myprofile" does not exist
为了尝试运行迁移，我尝试了:
docker-compose run web python manage.py makemigrations
docker-compose run web python manage.py migrate
返回以下内容:
Migrations for 'accounts':
accounts/migrations/0001_initial.py:
- Create model Entry
- Create model MyProfile
Running migrations:
No migrations to apply.
我只能从Django容器中成功迁移，例如:
docker exec -i -t 6dc97c6a305c /bin/bash
python manage.py makemigrations
python manage.py migrate
尽管我已经解决了问题，但我仍然不明白为什么通过docker-compose run运行迁移实际上并没有进行任何迁移.我希望有人可以为此指出正确的方向.
此外，我不知道这是否是一个相关问题，但是当我运行那些docker-compose run Web命令时，它们似乎正在创建不会关闭的新容器，除非我手动停止它们，docker -compose stop不会删除它们.
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
a7bb3c7106d1 accounts_web "python manage.py che" 4 hours ago Restarting (0) 41 minutes ago 8000/tcp accounts_web_run_62
ee19ca6cdf49 accounts_web "python manage.py mig" 4 hours ago Restarting (0) 43 minutes ago 8000/tcp accounts_web_run_60
2d87ee35de3a accounts_web "python manage.py mak" 4 hours ago Restarting (0) 43 minutes ago 8000/tcp accounts_web_run_59
1c6143c13097 accounts_web "python manage.py mig" 4 hours ago Restarting (1) 44 minutes ago 8000/tcp accounts_web_run_58
6dc97c6a305c b1cb7debb103 "python manage.py run" 3 days ago Up 4 hours 8000/tcp accounts_web_1
注意:Docker-compose stop将适当地在底部停止容器(应如此)，但是由docker-compose运行web python manage.py migration创建的其他容器将需要手动停止. /p>
我的docker-compose
web:
restart: always
build: ./web
expose:
- "8000"
links:
- postgres:postgres
volumes:
- /usr/src/app
- /usr/src/app/static
env_file: .env
environment:
DEBUG: 'true'
command: python manage.py runserver 0.0.0.0:8000
postgres:
restart: always
image: kartoza/postgis:9.4-2.1
ports:
- "5432:5432"
volumes:
- pgdata:/var/lib/postgresql/data/
docker-compose run创建新容器
您已经注意到了问题.使用docker-compose run时，将创建一个新容器.
运行第一个命令(makemigrations)时，将创建一个新容器，运行makemigrations，并将迁移文件写入到(新)容器的文件系统中.
运行第二个命令(迁移)时，将创建另一个新容器.迁移进行了，但是没有任何关系.那是因为迁移文件不可用-它们是在与新容器不同的容器中编写的.
您可以通过两种方法解决此问题.
使用docker-compose exec
首先，您可以做已经做的事情，但是使用docker-compose exec而不是run.
docker-compose exec web python manage.py makemigrations
docker-compose exec web python manage.py migrate
exec将使用已经运行的容器，而不是创建新的容器.
使用入口点脚本
另一种选择是在服务器启动之前，使用入口点脚本并在其中运行迁移.如果您希望事情变得更加自动化，这就是方法.
Dockerfile:
COPY entrypoint.sh /entrypoint.sh
RUN chmod +x /entrypoint.sh
entrypoint.sh:
#!/bin/sh
python manage.py makemigrations
python manage.py migrate
exec "$@"
docker-compose.yml(在网络"下):
entrypoint: /entrypoint.sh
在这种情况下，当容器启动时，入口点脚本将运行，处理您的迁移，然后移交给command(在本例中为Django runserver).
新容器永远循环
您注意到，新容器保持运行状态.这通常是意外的，因为您用应该退出(而不是保持运行状态)的命令覆盖了该命令.但是，在docker-compose.yml中，您指定了restart: always.因此，他们将一遍又一遍地运行迁移命令，并在每次退出命令时重新启动.
So I am deploying django, postgress and nginx containers via docker-compose and I have an issue that I can't seem to figure out.
In order to resolve the following error in my Django app, I knew I just had to run a Django migration.
docker@postgres ERROR: relation "accounts_myprofile" does not exist
In an attempt to run migrations, I tried:
docker-compose run web python manage.py makemigrations
docker-compose run web python manage.py migrate
which returned the following:
Migrations for 'accounts':
accounts/migrations/0001_initial.py:
- Create model Entry
- Create model MyProfile
Running migrations:
No migrations to apply.
I was only able to successfully migrate from within the Django container, example:
docker exec -i -t 6dc97c6a305c /bin/bash
python manage.py makemigrations
python manage.py migrate
Although I have resolved the issue, I still don't understand why running the migrate via docker-compose run does not actually migrate anything. I'm hoping someone can maybe point me in the right direction on this.
Also, I don't know if this is a related issue or not, but when I run those docker-compose run web commands, they seem to be creating new containers that won't shutdown unless I manually stop them, docker-compose stop doesn't remove them.
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
a7bb3c7106d1 accounts_web "python manage.py che" 4 hours ago Restarting (0) 41 minutes ago 8000/tcp accounts_web_run_62
ee19ca6cdf49 accounts_web "python manage.py mig" 4 hours ago Restarting (0) 43 minutes ago 8000/tcp accounts_web_run_60
2d87ee35de3a accounts_web "python manage.py mak" 4 hours ago Restarting (0) 43 minutes ago 8000/tcp accounts_web_run_59
1c6143c13097 accounts_web "python manage.py mig" 4 hours ago Restarting (1) 44 minutes ago 8000/tcp accounts_web_run_58
6dc97c6a305c b1cb7debb103 "python manage.py run" 3 days ago Up 4 hours 8000/tcp accounts_web_1
Note: Docker-compose stop will properly stop the container at the bottom (as it should), but the other container that were created by docker-compose run web python manage.py migrate, will need to be manually stopped.
my docker-compose
web:
restart: always
build: ./web
expose:
- "8000"
links:
- postgres:postgres
volumes:
- /usr/src/app
- /usr/src/app/static
env_file: .env
environment:
DEBUG: 'true'
command: python manage.py runserver 0.0.0.0:8000
postgres:
restart: always
image: kartoza/postgis:9.4-2.1
ports:
- "5432:5432"
volumes:
- pgdata:/var/lib/postgresql/data/
docker-compose run creates new containers
You have already noticed the problem. When you use docker-compose run, a new container is created.
When you ran the first command (makemigrations), a new container was created, makemigrations ran, and the migration files were written to the (new) container's filesystem.
When you ran the second command (migrate), another new container was created. The migration ran, but it had nothing to do. That's because the migration files were not available - they were written in a different container than this new one.
You can solve this in a couple of ways.
Using docker-compose exec
First, you can do what you already did, but use docker-compose exec instead of run.
docker-compose exec web python manage.py makemigrations
docker-compose exec web python manage.py migrate
exec will use the already-running container, rather than creating new containers.
Using an entrypoint script
Another option is to use an entrypoint script and run the migration there, before the server is started. This is the way to go if you'd prefer things to be more automatic.
Dockerfile:
COPY entrypoint.sh /entrypoint.sh
RUN chmod +x /entrypoint.sh
entrypoint.sh:
#!/bin/sh
python manage.py makemigrations
python manage.py migrate
exec "$@"
docker-compose.yml (under 'web'):
entrypoint: /entrypoint.sh
In this scenario, when the container starts, the entrypoint script will run, handle your migration, then hand off to the command (which in this case is Django runserver).
The new containers loop forever
As you noticed, the new containers stay running. That is normally unexpected, because you overrode the command with one that should exit (rather than stay running). However, in docker-compose.yml, you specified restart: always. So they will run the migration commands over and over, restarting each time the command exits.
这篇关于为什么我无法通过"docker-compose run web"命令运行django迁移?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
