profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/ndeloof/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Nicolas De loof ndeloof Docker Rennes, France http://blog.loof.fr Stuff Engineer

docker/compose 23484

Define and run multi-container applications with Docker

docker/awesome-compose 12920

Awesome Docker Compose samples

docker/cli 3041

The Docker CLI

compose-spec/compose-spec 923

The Compose specification

docker-archive/ecs-plugin 421

See http://github.com/docker/compose-cli

compose-spec/compose-go 151

Reference library for the parsing and loading Compose files

ndeloof/apache-maven-book 120

Apache Maven (le livre)

compose-spec/compose-ref 65

Compose specification reference implementation

docker-archive/cloud-integration-beta 30

Docker CLI with ACI integration (beta)

ndeloof/authobot 17

a docker authorization plugin to prevent abuses

PullRequestReviewEvent

push eventdocker/compose

Ulysses Souza

commit sha 436c588793ba4e9422e738e9d26e44e2f05d8f60

Bump containerd 1.5.5 Signed-off-by: Ulysses Souza <ulyssessouza@gmail.com>

view details

push time in 8 hours

PR merged docker/compose

Reviewers
Bump containerd 1.5.5
+14 -7

0 comment

2 changed files

ulyssessouza

pr closed time in 8 hours

PullRequestReviewEvent

issue closeddocker/compose

Install docker-compose v2.x system-wide

Description

How to install docker-compose v2.x system-wide instead of copying it into each users' home?

Steps to reproduce the issue:

  1. Download latest docker-compose release (which is 2.0.0 now).
  2. Copy it to /usr/local/bin/docker-compose
  3. chmod +x /usr/local/bin/docker-compose

Describe the results you received: None of docker-compose commands works. (docker-compose ps, docker-compose up, docker-compose down) All of them returns:

# docker-compose up

Usage:  docker [OPTIONS] COMMAND

docker-compose is a Docker CLI plugin

Options:
      --config string      Location of client config files (default "/root/.docker")
  -c, --context string     Name of the context to use to connect to the daemon (overrides DOCKER_HOST
                           env var and default context set with "docker context use")
  -D, --debug              Enable debug mode
  -H, --host list          Daemon socket(s) to connect to
  -l, --log-level string   Set the logging level ("debug"|"info"|"warn"|"error"|"fatal") (default "info")
      --tls                Use TLS; implied by --tlsverify
      --tlscacert string   Trust certs signed only by this CA (default "/root/.docker/ca.pem")
      --tlscert string     Path to TLS certificate file (default "/root/.docker/cert.pem")
      --tlskey string      Path to TLS key file (default "/root/.docker/key.pem")
      --tlsverify          Use TLS and verify the remote

Management Commands:
  completion                 generate the autocompletion script for the specified shell
  compose                    Docker Compose

Run 'docker COMMAND --help' for more information on a command.

To get more help with docker, check out our guides at https://docs.docker.com/go/guides/

Describe the results you expected: Install it system wide and it works.

Output of docker compose version:

docker-compose version does not work, but I've installed 2.0.0.

Output of docker info:

Client:
 Context:    default
 Debug Mode: false
 Plugins:
  app: Docker App (Docker Inc., v0.9.1-beta3)
  buildx: Build with BuildKit (Docker Inc., v0.6.1-docker)
  scan: Docker Scan (Docker Inc., v0.8.0)

Server:
 Containers: 2
  Running: 2
  Paused: 0
  Stopped: 0
 Images: 2
 Server Version: 20.10.8
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: e25210fe30a0a703442421b0f60afac609f950a3
 runc version: v1.0.1-0-g4144b63
 init version: de40ad0
 Security Options:
  seccomp
   Profile: default
 Kernel Version: 4.18.0-305.19.1.el8_4.x86_64
 Operating System: Rocky Linux 8.4 (Green Obsidian)
 OSType: linux
 Architecture: x86_64
 CPUs: 1
 Total Memory: 1.775GiB
 Name: hostname
 ID: OPO4:WFTW:WTD5:VTKN:NSLY:EHN6:2C6Y:5T3B:3XNK:QYIV:XTAV:EURV
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

closed time in 9 hours

aminvakil

issue commentdocker/compose

Install docker-compose v2.x system-wide

no you don't have to, this is all taking place on the CLI side Try docker compose version

aminvakil

comment created time in 9 hours

issue commentdocker/compose

Install docker-compose v2.x system-wide

nope, one of those

aminvakil

comment created time in 9 hours

issue commentdocker/compose

--env-file does not accept unix pipes

We indeed plan to mostly focus on Compose V2 codebase and V1 will get lower maintenance efforts, focussing on security/critical issues.

FranciscoDA

comment created time in 9 hours

delete branch ndeloof/compose

delete branch : checksum

delete time in 12 hours

push eventdocker/compose

Nicolas De Loof

commit sha 17d845b3d2e02ffccec465ee5039a3ec35957e61

compute sha256 checksums while releasing Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>

view details

push time in 12 hours

PR merged docker/compose

Reviewers
compute sha256 checksums while releasing

Related issue https://github.com/docker/compose/issues/8683

+3 -0

0 comment

1 changed file

ndeloof

pr closed time in 12 hours

issue closeddocker/compose

Checksum missing for 2.0.0 release

Description

https://github.com/docker/compose/releases/download/2.0.0/docker-compose-Linux-x86_64.sha256 is missing.

This (docker-compose-Linux-x86_64.sha256) used to be the filename though, maybe this needs to be changed to docker-compose-linux-amd64.sha256 from this release now on.

However that's missing too.

Steps to reproduce the issue:

  1. Try getting checksums for 2.0.0 release.

Describe the results you received: Missing :)

Describe the results you expected: Available :)

closed time in 12 hours

aminvakil

issue commentdocker/compose

Install docker-compose v2.x system-wide

docker compose V2 is a distinct architecture vs Compose V1 docker-compose is a Docker CLI plugin, should not be installed under /usr/local/bin but /usr/local/lib/docker/cli-plugins

aminvakil

comment created time in 12 hours

issue closeddocker/compose

Release File Names All Lowercase

While working with VS Code dev containers scripts (https://github.com/microsoft/vscode-dev-containers/issues/1075) I noticed that the new v2.0.0 release uses all lowercase file names where every other release had an initial cap for the platform name. Meaning what folks would expect to script up would be:

https://github.com/docker/compose/releases/download/v2.0.0/docker-compose-Linux-x86_64

This will 404 since the real working URL would be:

https://github.com/docker/compose/releases/download/v2.0.0/docker-compose-linux-x86_64

I'm guessing this might be a big problem for folks?

closed time in 12 hours

metaskills

issue commentdocker/compose

Release File Names All Lowercase

Docker compose V2 architecture and installation (docker CLI plugin) differs from Compose V1 (python), so you'll need to adjust your download script anyway.

metaskills

comment created time in 12 hours

issue commentdocker/compose

Make docker compose errors more verbose

Right. This worked because compose V1 uses python's dotenv library while we rely on godotenv which replicates ruby's dotenv library. Unfortunately dotenv is a de facto standard with no established format and rules, so better just keep it safe with quotes on ambiguous values

Dulanic

comment created time in 12 hours

issue closeddocker/compose

Make docker compose errors more verbose

<!-- If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.

If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.

For more information about reporting issues, see https://github.com/docker/compose-cli/blob/master/CONTRIBUTING.md#reporting-other-issues


GENERAL SUPPORT INFORMATION

The GitHub issue tracker is for bug reports and feature requests. General support can be found at the following locations:

  • Docker Support Forums - https://forums.docker.com
  • Docker Community Slack - https://dockr.ly/community
  • Post a question on StackOverflow, using the Docker tag

BUG REPORT INFORMATION

Use the commands below to provide key information from your environment: You do NOT have to include this information if this is a FEATURE REQUEST -->

<!-- Briefly describe the problem you are having in a few paragraphs. --> I am converting from docker-compose v1 to docker compose v2. v2 will not function in my use case. I cannot identify where the error is as the error is not helpful. I am guessing it is in my .env, but a line number would help? I'd like to give more info from my .env but that holds information I can't make public as would be expected in a .env file.

Steps to reproduce the issue: It is hard to say how to reproduce as I am just switching from v1 to v2 and --compatability does not help and I can't really make my .env file public.

Describe the results you received:

unexpected character "-" in variable name near "-l\n"

Describe the results you expected: It to function like it did in v1.

Additional information you deem important (e.g. issue happens only occasionally):

Output of docker compose version:

Docker Compose version v2.0.0

Output of docker info:

Client:
 Context:    default
 Debug Mode: false
 Plugins:
  app: Docker App (Docker Inc., v0.9.1-beta3)
  buildx: Build with BuildKit (Docker Inc., v0.6.1-docker)
  compose: Docker Compose (Docker Inc., v2.0.0)
  scan: Docker Scan (Docker Inc., v0.8.0)

Server:
 Containers: 50
  Running: 50
  Paused: 0
  Stopped: 0
 Images: 56
 Server Version: 20.10.8
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: e25210fe30a0a703442421b0f60afac609f950a3
 runc version: v1.0.1-0-g4144b63
 init version: de40ad0
 Security Options:
  apparmor
  seccomp
   Profile: default
 Kernel Version: 5.14.6-051406-generic
 Operating System: Ubuntu 20.04.3 LTS
 OSType: linux
 Architecture: x86_64
 CPUs: 6
 Total Memory: 15.5GiB
 Name: mediaserver
 ID: RKN6:Q4WI:HH6V:BMG5:U6FT:5BZ6:YB5Q:XJDD:D23S:RNFU:GWLF:FXX3
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

Additional environment details:

closed time in 12 hours

Dulanic

issue commentdocker/compose

Checksum missing for 2.0.0 release

v2.0.0 is a distinct, Golang codebase and so applies related conventions. Installation is not the same as docker-compose V1 (V2 is a CLI plugin), so your script probably will need to be updated anyway.

I fixed the checksum oin v2.0.0 - this is what happen when not using an automated process :'(

aminvakil

comment created time in 12 hours

push eventndeloof/compose

Nicolas De Loof

commit sha 1e6498320ce38a47d6a43f42f1e3f7bfe454dc10

compute sha256 checksums while releasing Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>

view details

push time in 12 hours

issue commentdocker/compose

Make docker compose errors more verbose

please try to drop some variables from your .env file until you can provide a reproduction example

Dulanic

comment created time in 12 hours

issue closeddocker/compose

security_opt and seccomp with files broken in v2

I'd like to be able to use seccomp files in v2.

See https://github.com/docker/compose/issues/5574 for the original v1 issue, which was addressed in https://github.com/docker/compose/pull/5701

With v2, the same compose file results in this error:

Error response from daemon: Decoding seccomp profile failed: json: cannot unmarshal string into Go value of type seccomp.Seccomp

closed time in 12 hours

sah

issue commentdocker/compose

security_opt and seccomp with files broken in v2

Make me think this should be defined and documented by the Compose Specification => https://github.com/compose-spec/compose-spec/issues/203

sah

comment created time in 12 hours

issue openedcompose-spec/compose-spec

Better document security options

What is the problem you're trying to solve According to the compose specification:

security_opt overrides the default labeling scheme for each container.

but actually, even this is not documented by the Docker Engine API (which only declare this as "A list of string values to customize labels for MLS systems, such as SELinux") it can be used to pass a seccomp or apparmor profile, or set no-new-privileges as documented on https://docs.docker.com/engine/reference/run/#security-configuration.

While this might not be portable, so might be considered "implementation-specific", support for seccomp profile has impact as this one is a PATH, and as such need to be considered relative to the compose project working directory. Also, according to https://github.com/docker/cli/blob/9de1b162f/cli/command/container/opts.go#L683-L692, such a seccomp profile is actually read from client and passed as JSON, so need client-side processing.

Describe the solution you'd like security_opt to better define known options, and special seccomp case to be handled by implementations.

Additional context https://github.com/docker/compose/issues/8678

created time in 12 hours

issue commentdocker/compose

run.sh missing for 2.0.0 release

run.sh is a Compose V1 feature, using a Docker image to workaround the need for a python runtime to execute docker-compose. Compose V2 being a CLI plugin, and a plain binary cross-compiled for all systems, this isn't considered required anymore.

modem7

comment created time in 13 hours

issue commentdocker/compose

Make docker compose errors more verbose

it seems your .env file declares some variable with an hyphen in name, which is invalid (dot env file should also be applied as plain bash variables)

see https://github.com/docker/compose/issues/8507

Dulanic

comment created time in 13 hours

issue commentdocker/compose

docker --context remotehost compose up -d shows WARN[0006] commandConn.CloseWrite

for the records: https://github.com/docker/cli/blob/master/cli/connhelper/commandconn/commandconn.go#L203-L214

StefanScherer

comment created time in 13 hours

issue closeddocker/compose

ssh DOCKER_HOST hangs -> leads to connection time outs

<!-- Welcome to the docker-compose issue tracker! Before creating an issue, please heed the following:

  1. This tracker should only be used to report bugs and request features / enhancements to docker-compose
    • For questions and general support, use https://forums.docker.com
    • For documentation issues, use https://github.com/docker/docker.github.io
    • For issues with the docker stack commands and the version 3 of the Compose file, use https://github.com/docker/cli
  2. Use the search function before creating a new issue. Duplicates will be closed and directed to the original discussion.
  3. When making a bug report, make sure you provide all required information. The easier it is for maintainers to reproduce, the faster it'll be fixed. -->

Description of the issue

When I set up a remote connection by DOCKER_HOST=ssh://... or using a context remote, I am at least 1 time able to run docker-compose up --build --force-recreate. As it happens one container exits with a error code, so I have to quit by pressing Ctrl+C. This gives me

proxy exited with code 1
^CGracefully stopping... (press Ctrl+C again to force)
WARN[0342] commandConn.CloseWrite: commandconn: failed to wait: signal: killed
WARN[0342] commandConn.CloseWrite: commandconn: failed to wait: signal: killed
WARN[0342] commandConn.CloseWrite: commandconn: failed to wait: signal: killed
WARN[0342] commandConn.CloseWrite: commandconn: failed to wait: signal: killed
[+] Running 0/3
[+] Running 3/3bportal  Stopping                                                                                                                                            1.3s
 ⠿ Container webportal  Stopped                                                                                                                                             1.5s 
 ⠿ Container proxy      Stopped                                                                                                                                             1.3s 
 ⠿ Container bootstrap  Stopped                                                                                                                                             2.3s
WARN[0345] commandConn.CloseWrite: commandconn: failed to wait: signal: killed
canceled

Afterwards I am not able to start again, even a ssh connection directly by ssh -i key user@ip is mostly not possible (not always).

Context information (for bug reports)

  • [x] Using Compose V2 docker compose ...
  • [ ] Using Compose V1 docker-compose ...

Output of docker(-)compose version

Docker Compose version v2.0.0-rc.3

Output of docker version

Client: Docker Engine - Community
 Cloud integration: 1.0.17
 Version:           20.10.8
 API version:       1.41
 Go version:        go1.16.6
 Git commit:        3967b7d
 Built:             Fri Jul 30 19:54:02 2021
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.8
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.16.6
  Git commit:       75249d8
  Built:            Fri Jul 30 19:52:00 2021
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.4.9
  GitCommit:        e25210fe30a0a703442421b0f60afac609f950a3
 runc:
  Version:          1.0.1
  GitCommit:        v1.0.1-0-g4144b63
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Steps to reproduce the issue

  1. DOCKER_HOST=ssh://user@ip
  2. eval "$(ssh-agent)"
  3. ssh-add ~/.ssh/key_rsa
  4. docker-compse up --build --force-recreate
  5. Ctrl+C
  6. docker-compse up --build --force-recreate

Observed result

WARN[0001] commandConn.CloseWrite: commandconn: failed to wait: signal: killed 
[+] Building 0.0s (0/0)
failed to get status: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing command [ssh -l user -- x.x.x.x docker system dial-stdio] has exited with exit status 255, please make sure the URL is valid, and Docker 18.09 or later is installed on the remote host: stderr=ssh: connect to host x.x.x.x port 22: Connection timed out\r\n"

Expected result

Work everytime, I don't see this problem on local. I am still always able to connect by ssh via Putty, so I definitely know, the connection should work.

Additional information

I am using Win10 with WSL Ubuntu 20.04.3 LTS, remote CentOS7 and CentOS8, Visual Studio Code 1.60.2

closed time in 13 hours

MLEI-AERO

issue commentdocker/compose

ssh DOCKER_HOST hangs -> leads to connection time outs

duplicates https://github.com/docker/compose/issues/8544

MLEI-AERO

comment created time in 13 hours

issue commentdocker/compose

Checksum missing for 2.0.0 release

I fixed this manually for 2.0.0 release and proposed https://github.com/docker/compose/pull/8685 to get this generated automatically during release process

aminvakil

comment created time in 13 hours

PR opened docker/compose

compute sha256 checksums while releasing

Related issue https://github.com/docker/compose/issues/8683

+3 -0

0 comment

1 changed file

pr created time in 13 hours