在docker容器中启动docker compose时卷不工作

在docker容器中启动docker compose时卷不工作,docker,docker-compose,volume,mount,Docker,Docker Compose,Volume,Mount,我目前正在尝试从另一个docker容器中运行docker容器(当然,从主机将/var/run/docker.sock装入容器1)。我正在从那里克隆另一个存储库,并尝试启动在docker compose.ymlcontainer2中定义的一个容器。因此,最终容器将在主机(即Mac btw)上并行运行。但是,当启动第二个容器时,它只是退出并显示错误消息 ERROR: for container2_1 Cannot start service php_apache: OCI runtime crea

我目前正在尝试从另一个docker容器中运行docker容器(当然,从主机将
/var/run/docker.sock
装入
容器1
)。我正在从那里克隆另一个存储库,并尝试启动在
docker compose.yml
container2
中定义的一个容器。因此,最终容器将在主机(即Mac btw)上并行运行。但是,当启动第二个容器时,它只是退出并显示错误消息

ERROR: for container2_1  Cannot start service php_apache: OCI runtime create failed: container_linux.go:349: starting container process caused "process_linux.go:449: container init caused \"rootfs_linux.go:58: mounting \\\"/usr/src/repository2/docker/apache/ports.conf\\\" to rootfs \\\"/var/lib/docker/overlay2/7916ca725ce4218720950cea152c3efbdfe1143d/merged\\\" at \\\"/var/lib/docker/overlay2/7916ca725ce4218720950cea152c3efbdfe1143d/merged/etc/apache2/ports.conf\\\" caused \\\"not a directory\\\"\"": unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type
我已经尝试将克隆的存储库移动到单独的卷中,但这并没有解决问题。从主机装载此目录也不起作用

repository1-
docker compose.yml

version: "3.7"

volumes:
  container1-volume:

services:
  container1:
    image: python:3.8.6-buster
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - ./:/usr/src/app
      - container1-volume:/usr/src/container1
    working_dir: /usr/src/app/python_db
    command: ./startup.sh

version: "3.7"

services:
  container2:
    working_dir: /var/www
    image: php:7.2-apache
    volumes:
      - ./docker/apache/000-default-backend.conf:/etc/apache2/sites-available/000-default.conf
      - ./docker/apache/ports.conf:/etc/apache2/ports.conf
      - .:/var/www/:delegated
      - ./docker/php/php.ini:/usr/local/etc/php/php.ini
[...]
repository1-
startup.sh

APPLICATION_DIR=/usr/src/container1

rm -Rf $APPLICATION_DIR/*
rm -Rf $APPLICATION_DIR/.*

git \
  clone \
  --single-branch \
  --branch $BRANCH \
  https://$BITBUCKET_USERNAME:$BITBUCKET_APP_PASSWORD@bitbucket.org/vendor/repository2.git \
  $APPLICATION_DIR

(cd $APPLICATION_DIR && docker-compose up --no-deps container2)
repository2-
docker compose.yml

version: "3.7"

volumes:
  container1-volume:

services:
  container1:
    image: python:3.8.6-buster
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - ./:/usr/src/app
      - container1-volume:/usr/src/container1
    working_dir: /usr/src/app/python_db
    command: ./startup.sh

version: "3.7"

services:
  container2:
    working_dir: /var/www
    image: php:7.2-apache
    volumes:
      - ./docker/apache/000-default-backend.conf:/etc/apache2/sites-available/000-default.conf
      - ./docker/apache/ports.conf:/etc/apache2/ports.conf
      - .:/var/www/:delegated
      - ./docker/php/php.ini:/usr/local/etc/php/php.ini
[...]
当直接在主机上执行repository2的docker compose文件时,它已经完美地工作了一年多了

docker容器中的文件是如何处理的,我有什么遗漏吗?是否需要更改特定权限以避免文件目录不匹配