docker compose-up——在入口点chown构建挂起，没有错误.如何解决

Question

我试图在启动时更改已装入卷的所有权，以便容器中的用户可以向其写入，主机可以从中读取。

volumes:
- '../local/userData:/userData'

似乎被接受了-在local/userData中创建了一个文件夹，但作为根文件夹。entryPoint命令中的sudo chown -R user:user /userData似乎失败并挂起，没有出现错误。如何解决这个问题？

...
services:
myservice:
build:
context: ..
dockerfile: myservice-container/Dockerfile
image: myservice:latest
container_name: local_myservice_1
networks:
- local_default
volumes:
- '../local/userData:/userData'
environment:
DEPLOY_TYPE: local
AWS_ENVIRONMENT: NOT_AWS
cap_add:
- NET_ADMIN
stdin_open: true
tty: true
# Make /userData writeable to user.
entrypoint: sh -c "(ls -la /userData) && (sudo chown -R user:user /userData) && (echo OK)"

dockerfile已成功创建用户：

RUN useradd -ms /bin/bash user

整个过程挂起：

Recreating myservice_1 ... done
Attaching to myservice_1
myservice_1  | total 8
myservice_1  | drwxr-xr-x 2 root root 4096 Jul 29 15:20 .
myservice_1  | drwxr-xr-x 1 root root 4096 Jul 29 15:27 ..
compose.cli.verbose_proxy.proxy_callable: docker events -> <docker.types.daemon.CancellableStream object at 0x7f7b815604f0>
....<hangs here> ....
^C
compose.parallel.feed_queue: Pending: set()
compose.parallel.feed_queue: Pending: set()
compose.parallel.feed_queue: Pending: set()
compose.parallel.feed_queue: Pending: set()
^Ccompose.cli.verbose_proxy.proxy_callable: docker containers <- (all=False, filters={'label': ['com.docker.compose.project=local', '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 <- ('7f39ec0d3a5019b72ff42b13eb7a0353c420c35738c0be5d6a4f80b95fde8102')
compose.cli.verbose_proxy.proxy_callable: docker inspect_container -> {'AppArmorProfile': 'docker-default',
'Args': ['-c',
'(ls -la /userData) && (sudo chown -R user:user /userData) && (echo '
'OK)'],
'Config': {'AttachStderr': False,
'AttachStdin': False,
'AttachStdout': False,
'Cmd': None,
'Domainname': '',
'Entrypoint': ['sh',
...
Killing myservice_1    ... 
compose.parallel.feed_queue: Pending: {<Container: local_ai_1 (7f39ec)>}
compose.parallel.feed_queue: Starting producer thread for <Container: myservice_1 (7f39ec)>
compose.cli.verbose_proxy.proxy_callable: docker kill <- ('7f39ec0d3a5019b72ff42b13eb7a0353c420c35738c0be5d6a4f80b95fde8102')
compose.cli.verbose_proxy.proxy_callable: docker inspect_container <- ('7f39ec0d3a5019b72ff42b13eb7a0353c420c35738c0be5d6a4f80b95fde8102')
compose.cli.verbose_proxy.proxy_callable: docker inspect_container -> {'AppArmorProfile': 'docker-default',
'Args': ['-c',
'(ls -la /userData) && (sudo chown -R user:user /userData) && (echo '
'OK)'],
'Config': {'AttachStderr': False,
'AttachStdin': False,
'AttachStdout': False,
'Cmd': None,
'Domainname': '',
'Entrypoint': ['sh',
...
compose.parallel.feed_queue: Pending: set()
compose.cli.verbose_proxy.proxy_callable: docker wait <- ('7f39ec0d3a5019b72ff42b13eb7a0353c420c35738c0be5d6a4f80b95fde8102')
compose.cli.verbose_proxy.proxy_callable: docker inspect_container <- ('7f39ec0d3a5019b72ff42b13eb7a0353c420c35738c0be5d6a4f80b95fde8102')
compose.parallel.feed_queue: Pending: set()
compose.parallel.feed_queue: Pending: set()
compose.parallel.feed_queue: Pending: set()
compose.parallel.feed_queue: Pending: set()
compose.cli.verbose_proxy.proxy_callable: docker kill -> None
compose.cli.verbose_proxy.proxy_callable: docker stop -> None
Killing myservice_1    ... done
compose.cli.verbose_proxy.proxy_callable: docker wait -> {'Error': None, 'StatusCode': 137}
compose.cli.verbose_proxy.proxy_callable: docker inspect_container -> {'AppArmorProfile': 'docker-default',
'Args': ['-c',
'(ls -la /userData) && (sudo chown -R user:user /userData) && (echo '
'OK)'],
'Config': {'AttachStderr': False,
'AttachStdin': False,
'AttachStdout': False,
'Cmd': None,
'Domainname': '',
'Entrypoint': ['sh',
...
compose.parallel.feed_queue: Pending: set()
compose.cli.verbose_proxy.proxy_callable: docker inspect_container <- ('7f39ec0d3a5019b72ff42b13eb7a0353c420c35738c0be5d6a4f80b95fde8102')
ERROR: compose.cli.main.exit_with_metrics: 2
compose.cli.verbose_proxy.proxy_callable: docker inspect_container -> {'AppArmorProfile': 'docker-default',
'Args': ['-c',
'(ls -la /userData) && (sudo chown -R user:user /userData) && (echo '
'OK)'],
'Config': {'AttachStderr': False,
'AttachStdin': False,
'AttachStdout': False,
'Cmd': None,
'Domainname': '',
'Entrypoint': ['sh',

"OK"；未打印。我正在运行docker-compose --verbose up --build

---

没有解决：docker组成永远挂起。如何调试，docker compose up error without information，docker compose&docker入口点，docker永远挂断。如何调试？

Answer 1

简单的解决方案是始终让主机创建该文件夹，而不是让docker编写。如果docker compose创建了它，那么它将被创建为root。