Closed itssadon closed 5 years ago
Fixed in master branch and present in docker-compose 1.25.0-rc1
...
debconf: delaying package configuration, since apt-utils is not installed
Fetched 120 MB in 2min 9s (926 kB/s)
Selecting previously unselected package libapparmor1:amd64.
(Reading database ... 24555 files and directories currently installed.)
Preparing to unpack .../0-libapparmor1_2.13.2-10_amd64.deb ...
Unpacking libapparmor1:amd64 (2.13.2-10) ...
Selecting previously unselected package libargon2-1:amd64.
Preparing to unpack .../1-libargon2-1_0~20171227-0.2_amd64.deb ...
Unpacking libargon2-1:amd64 (0~20171227-0.2) ...
Selecting previously unselected package dmsetup.
Preparing to unpack .../2-dmsetup_2%3a1.02.155-3_amd64.deb ...
Unpacking dmsetup (2:1.02.155-3) ...
Selecting previously unselected package libdevmapper1.02.1:amd64.
Preparing to unpack .../3-libdevmapper1.02.1_2%3a1.02.155-3_amd64.deb ...
Unpacking libdevmapper1.02.1:amd64 (2:1.02.155-3) ...
Selecting previously unselected package libjson-c3:amd64.
Preparing to unpack .../4-libjson-c3_0.12.1+ds-2_amd64.deb ...
Unpacking libjson-c3:amd64 (0.12.1+ds-2) ...
Selecting previously unselected package libcryptsetup12:amd64.
Preparing to unpack .../5-libcryptsetup12_2%3a2.1.0-5+deb10u2_amd64.deb ...
Unpacking libcryptsetup12:amd64 (2:2.1.0-5+deb10u2) ...
Selecting previously unselected package libidn11:amd64.
Preparing to unpack .../6-libidn11_1.33-2.2_amd64.deb ...
Unpacking libidn11:amd64 (1.33-2.2) ...
Selecting previously unselected package libip4tc0:amd64.
Preparing to unpack .../7-libip4tc0_1.8.2-4_amd64.deb ...
Unpacking libip4tc0:amd64 (1.8.2-4) ...
Selecting previously unselected package libkmod2:amd64.
Preparing to unpack .../8-libkmod2_26-1_amd64.deb ...
Unpacking libkmod2:amd64 (26-1) ...
Selecting previously unselected package systemd.
Preparing to unpack .../9-systemd_241-7~deb10u2_amd64.deb ...
Unpacking systemd (241-7~deb10u2) ...
Setting up libapparmor1:amd64 (2.13.2-10) ...
Setting up libargon2-1:amd64 (0~20171227-0.2) ...
Setting up libjson-c3:amd64 (0.12.1+ds-2) ...
Setting up libidn11:amd64 (1.33-2.2) ...
Setting up libip4tc0:amd64 (1.8.2-4) ...
Setting up libkmod2:amd64 (26-1) ...
Setting up libdevmapper1.02.1:amd64 (2:1.02.155-3) ...
Setting up libcryptsetup12:amd64 (2:2.1.0-5+deb10u2) ...
Setting up systemd (241-7~deb10u2) ...
Created symlink /etc/systemd/system/getty.target.wants/getty@tty1.service ??/lib/systemd/system/getty@.service.
Traceback (most recent call last):
File "docker-compose", line 6, in
==================================
Same problem when I use devcontainer in vs-code, in the process of building Dockerfile.
Then I tried docker-compose up
, same problem.
Then I tried docker build .
, succeed.
docker-compose version
docker-compose version 1.25.2, build 698e2846
docker-py version: 4.1.0
CPython version: 2.7.16
OpenSSL version: OpenSSL 1.0.2q 20 Nov 2018
docker version
Client: Docker Engine - Community
Version: 19.03.5
API version: 1.40
Go version: go1.12.12
Git commit: 633a0ea
Built: Wed Nov 13 07:22:37 2019
OS/Arch: windows/amd64
Experimental: false
Server: Docker Engine - Community
Engine:
Version: 19.03.4
API version: 1.40 (minimum version 1.12)
Go version: go1.12.10
Git commit: 9013bf583a
Built: Fri Oct 18 15:50:54 2019
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.2.10
GitCommit: b34a5c8af56e510852c35414db4c1f4fa6172339
runc:
Version: 1.0.0-rc8+dev
GitCommit: 3e425f80a8c931f88e6d94a8c831b9d5aa481657
docker-init:
Version: 0.18.0
GitCommit: fec3683
docker-compose config
WARNING: Some services (get_data) use the 'deploy' key, which will be ignored. Compose does not support 'deploy' configuration - use `docker stack deploy` to deploy to a swarm.
networks:
internal: {}
mongo_replica:
driver: overlay
name: mongo_replica
services:
get_data:
build:
args:
serv_user: xxx
context: D:\git\xxx\.devcontainer
dockerfile: Dockerfile
cap_add:
- SYS_PTRACE
command: bash -c "mkdir -p /root/.ssh; cp /workspace/devcontainers/.gitconfig
/root/.gitconfig; cp /workspace/devcontainers/.ssh/* /root/.ssh/; chmod 600
/root/.ssh/id_rsa; chmod 700 /root/.ssh; sleep infinity"
container_name: get_data
deploy:
placement:
constraints:
- node.role == manager
replicas: 1
resources:
limits:
cpus: '3'
memory: 3072M
reservations:
cpus: '0.5'
memory: 512M
restart_policy:
condition: on-failure
delay: 5s
max_attempts: 3
window: 120s
image: python_get_data
networks:
internal: null
mongo_replica: null
security_opt:
- seccomp:unconfined
shm_size: 2g
volumes:
- dev_code_volume:/workspace:rw
- /var/run/docker.sock:/var/run/docker.sock:rw
- /:/hostfs:rw
- jupyter_volume:/jupyter:rw
version: '3.7'
volumes:
dev_code_volume:
external: true
name: dev_code_volume
dev_data_volume:
name: dev_data_volume
jupyter_volume:
name: jupyter_volume
Created symlink /etc/systemd/system/getty.target.wants/getty@tty1.service 鈫?/lib/systemd/system/getty@.service.
Traceback (most recent call last):
File "docker-compose", line 6, in <module>
File "compose\cli\main.py", line 72, in main
File "compose\cli\main.py", line 128, in perform_command
File "compose\cli\main.py", line 1077, in up
File "compose\cli\main.py", line 1073, in up
File "compose\project.py", line 548, in up
[93292 ms]
File "compose\service.py", line 351, in ensure_image_exists
File "compose\service.py", line 1110, in build
File "compose\progress_stream.py", line 30, in stream_output
File "compose\progress_stream.py", line 95, in print_output_event
File "compose\progress_stream.py", line 13, in write_to_stream
File "codecs.py", line 370, in write
File "site-packages\colorama\ansitowin32.py", line 41, in write
File "site-packages\colorama\ansitowin32.py", line 162, in write
File "site-packages\colorama\ansitowin32.py", line 190, in write_and_convert
File "site-packages\colorama\ansitowin32.py", line 195, in write_plain_text
IOError: [Errno 0] Error
[22900] Failed to execute script docker-compo
[22900] Failed to execute script docker-compose
@FreelanceDev217 and @alexgzhou .
Could you please try to reproduce that with docker-compose 1.25.4
?
If yes, please create another issue including your configuration files and .env
(if existent)
it seem happen with profiles: [xx, yy]
,
1 docker-compose --profile xx up -d A
2 then edit yaml
3 docker-compose up -d A
solve: docker-compose down and up again
Description of the issue
Context information (for bug reports)
Output of
docker-compose version
Output of
docker version
Output of
docker-compose config
(Make sure to add the relevant-f
and other flags)Steps to reproduce the issue
docker-compose up -d
docker-compose ps -a
docker-compose --verbose ps -a
Observed result
Traceback (most recent call last): File "docker-compose", line 6, in
File "compose/cli/main.py", line 71, in main
File "compose/cli/main.py", line 127, in perform_command
File "compose/cli/main.py", line 712, in ps
TypeError: '<' not supported between instances of 'Container' and 'Container'
[29233] Failed to execute script docker-compose
Expected result
Show all stopped containers (including those created by the run command)
Stacktrace / full error message
Additional information
OS version / distribution,
docker-compose
install method, etc.