image - 使用docker-compose创建容器会删除另一个已经运行的容器

Question

我试图基于2个不同的图像使用docker-compose命令启动2个单独的容器。

一个图像(作品)基于“开发”中处理的代码。第二个图像(cons)图像由当前处于“合并”级别的代码创建。

启动第一个容器时，一切似乎正常。



上图的详细信息在这里:

工作目录:〜/ apps / django.work / extraction / docker-compose.yml

version: '3'

services:
  db:
    image: postgres
    container_name: postgres-work           
  web:
    build: .
    image: apostx-cc-backoffice-work        
    container_name: cc-backoffice-work      
    command: python3 backendworkproj/manage.py runserver 0.0.0.0:8000
    volumes:
      - .:/code
    ports:
      - "7350:8000"
    depends_on:
      - db

执行:〜/ apps / django.work。/ extraction $ docker-compose up --no-deps -d web

Creating network "extraction_default" with the default driver
Creating cc-backoffice-work ...
Creating cc-backoffice-work ... done

执行:〜/ apps / django.work / extraction $ docker容器ls

CONTAINER ID        IMAGE                       COMMAND                  CREATED             STATUS              PORTS                    NAMES
39185f36941a        apostx-cc-backoffice-work   "python3 backendwo..."   8 seconds ago       Up 7 seconds        0.0.0.0:7350->8000/tcp   cc-backoffice-work
dede5cb1966a        jarkt/docker-remote-api     "/bin/sh -c 'socat..."   2 days ago          Up 2 days           0.0.0.0:3080->2375/tcp   dock_user_display_remote

但是，当我使用第二个目录编译并启动另一个镜像时，一些奇怪的事情开始发生:



同样，更多详细信息如下:

缺点目录:〜/ apps / django.cons / extraction / docker-compose.yml

version: '3'

services:
  db:
    image: postgres
    container_name: postgres-cons         
  web:
    build: .
    image: apostx-cc-backoffice-cons      
    container_name: cc-backoffice-cons    
    command: python3 backendworkproj/manage.py runserver 0.0.0.0:8000
    volumes:
      - .:/code
    ports:
      - "7450:8000"
    depends_on:
      - db

执行:〜/ apps / django.cons / extraction $ docker-compose up --no-deps -d web

Recreating cc-backoffice-work ...
Recreating cc-backoffice-work
Recreating cc-backoffice-work ... done

执行:〜/ apps / django.cons / extraction $ docker容器ls

CONTAINER ID        IMAGE                       COMMAND                  CREATED             STATUS              PORTS                    NAMES
f942f84e567a        apostx-cc-backoffice-cons   "python3 backendwo..."   7 seconds ago       Up 6 seconds        0.0.0.0:7450->8000/tcp   cc-backoffice-cons
dede5cb1966a        jarkt/docker-remote-api     "/bin/sh -c 'socat..."   2 days ago          Up 2 days           0.0.0.0:3080->2375/tcp   dock_user_display_remote

题

为什么在我启动第二个容器时会替换第一个容器？如果是由于某种缓存问题引起的，那么在第二次运行 docker-compose之前如何重新初始化/清理/清除缓存？我在这里想念什么吗？

TIA

更新-我做了以下工作:

1. got rid of old containers by using "docker container rm -f "

--

2. started the "work" (i.e. development) container

执行:〜/ apps / django.work.ccbo.thecontractors.club / extraction $ docker-compose --verbose up --no-deps -d web>＆the_results_are_here

执行:〜/ apps / django.work.ccbo.thecontractors.club / extraction $ docker容器ls

CONTAINER ID        IMAGE                       COMMAND                  CREATED             STATUS              PORTS                    NAMES
61d2e9ccbc28        apostx-cc-backoffice-work   "python3 backendwo..."   4 seconds ago       Up 4 seconds        0.0.0.0:7350->8000/tcp   work-cc-backoffice
dede5cb1966a        jarkt/docker-remote-api     "/bin/sh -c 'socat..."   3 days ago          Up 3 days           0.0.0.0:3080->2375/tcp   dock_user_display_remote
9b4b8b462fcb        wmaker-test-officework      "catalina.sh run"        11 days ago         Up 11 days          0.0.0.0:7700->8080/tcp   testBackOfficeWork.2017.10.30.04.20.01
ad5fd0592a07        wmaker-locl-officework      "catalina.sh run"        11 days ago         Up 11 days          0.0.0.0:7500->8080/tcp   loclBackOfficeWork.2017.10.30.04.20.01
7bc9d7f94828        wmaker-cons-officework      "catalina.sh run"        11 days ago         Up 11 days          0.0.0.0:7600->8080/tcp   consBackOfficeWork.2017.10.30.04.20.01

3. seeing that it looks OK, started the container for "cons" (consolidation)

执行:〜/ apps / django.cons.ccbo.thecontractors.club / extraction $ docker-compose --verbose up --no-deps -d web>＆the_results_are_here

执行:〜/ apps / django.cons.ccbo.thecontractors.club / extraction $ docker容器ls

CONTAINER ID        IMAGE                       COMMAND                  CREATED             STATUS              PORTS                    NAMES
0fb24fc45877        apostx-cc-backoffice-cons   "python backendwor..."   5 seconds ago       Up 4 seconds        0.0.0.0:7450->8010/tcp   cons-cc-backoffices
dede5cb1966a        jarkt/docker-remote-api     "/bin/sh -c 'socat..."   3 days ago          Up 3 days           0.0.0.0:3080->2375/tcp   dock_user_display_remote
9b4b8b462fcb        wmaker-test-officework      "catalina.sh run"        11 days ago         Up 11 days          0.0.0.0:7700->8080/tcp   testBackOfficeWork.2017.10.30.04.20.01
ad5fd0592a07        wmaker-locl-officework      "catalina.sh run"        11 days ago         Up 11 days          0.0.0.0:7500->8080/tcp   loclBackOfficeWork.2017.10.30.04.20.01
7bc9d7f94828        wmaker-cons-officework      "catalina.sh run"        11 days ago         Up 11 days          0.0.0.0:7600->8080/tcp   consBackOfficeWork.2017.10.30.04.20.01

4. Again, the name: work-cc-backoffice has been supplanted by name: cons-cc-backoffices - work-cc-backoffice is totally gone now.

--

5. Looked at the file the_results_are_here (in the second run) to see if anything can be found

[... snip ...]

compose.cli.command.get_client: docker-compose version 1.17.1, build 6d101fb
docker-py version: 2.5.1
CPython version: 2.7.13
OpenSSL version: OpenSSL 1.0.1t  3 May 2016
compose.cli.command.get_client: Docker base_url: http+docker://localunixsocket
compose.cli.command.get_client: Docker version: KernelVersion=4.4.0-72-generic, Arch=amd64, BuildTime=2017-09-26T22:40:56.000000000+00:00, ApiVersion=1.32, Version=17.09.0-ce, MinAPIVersion=1.12, GitCommit=afdb6d4, Os=linux, GoVersion=go1.8.3
compose.cli.verbose_proxy.proxy_callable: docker info <- ()
compose.cli.verbose_proxy.proxy_callable: docker info -> {u'Architecture': u'x86_64',

[... snip ...]

compose.cli.verbose_proxy.proxy_callable: docker inspect_network <- (u'extraction_default')
compose.cli.verbose_proxy.proxy_callable: docker inspect_network -> {u'Attachable': True,
 u'ConfigFrom': {u'Network': u''},
 u'ConfigOnly': False,
 u'Containers': {u'61d2e9ccbc28bb2aba918dc24b5f19a3f68a06b9502ec1b98e83dd947d75d1be': {u'EndpointID': u'e19696ccf258a6cdcfcce41d91d5b3ebcb5fffbce4257e3480ced48a3d7dcc5c',
                                                                                       u'IPv4Address': u'172.20.0.2/16',
                                                                                       u'IPv6Address': u'',
                                                                                       u'MacAddress': u'02:42:ac:14:00:02',
                                                                                       u'Name': u'work-cc-backoffice'}},
 u'Created': u'2017-11-10T09:56:22.709914332Z',

 u'Driver': u'bridge',
...
compose.cli.verbose_proxy.proxy_callable: docker containers <- (all=False, filters={u'label': [u'com.docker.compose.project=extraction', u'com.docker.compose.oneoff=False']})
compose.cli.verbose_proxy.proxy_callable: docker containers -> (list with 1 items)
compose.cli.verbose_proxy.proxy_callable: docker inspect_container <- (u'61d2e9ccbc28bb2aba918dc24b5f19a3f68a06b9502ec1b98e83dd947d75d1be')
compose.cli.verbose_proxy.proxy_callable: docker inspect_container -> {u'AppArmorProfile': u'docker-default',
 u'Args': [u'backendworkproj/manage.py', u'runserver', u'0.0.0.0:8000'],
 u'Config': {u'AttachStderr': False,
             u'AttachStdin': False,
             u'AttachStdout': False,
             u'Cmd': [u'python3',
                      u'backendworkproj/manage.py',
                      u'runserver',
                      u'0.0.0.0:8000'],
             u'Domainname': u'',
...
compose.cli.verbose_proxy.proxy_callable: docker containers <- (all=True, filters={u'label': [u'com.docker.compose.project=extraction', u'com.docker.compose.service=web', u'com.docker.compose.oneoff=False']})
compose.cli.verbose_proxy.proxy_callable: docker containers -> (list with 1 items)
compose.cli.verbose_proxy.proxy_callable: docker inspect_container <- (u'61d2e9ccbc28bb2aba918dc24b5f19a3f68a06b9502ec1b98e83dd947d75d1be')
compose.cli.verbose_proxy.proxy_callable: docker inspect_container -> {u'AppArmorProfile': u'docker-default',

To me, it looks like the program is trying to do some initialization by looking for a container that is already up and running(?) See pic. below. How can one change this behavior

Answer 1

@mikeyjk的答复解决了该问题。

No worries. I wonder if you give each service a unique name, re run composer build, whether the issue still occurs. I'll try and replicate it today if no-one can work it out