Closed christopher-hopper closed 2 years ago
I'm happy to review and merge this on the premise of it being a documentation improvement - however it should be noted and clarified that pygmy-go
has absolutely no dependence on docker-compose
. Docker Compose is a separate application which talks to the Docker API - just like Pygmy.
Individual projects which utilize docker-compose
will need to be updated to support docker-compose
v2. But, that makes zero difference to pygmy-go
and this can be observed in Pygmy's rigorous self-testing - an example of you demonstrating this working from your output:
- http://docker.amazee.io/stats (amazeeio-haproxy)
- http://mailhog.docker.amazee.io (amazeeio-mailhog)
I'll start reviewing the PR, but please make sure the issue title reflects the proposed changes that will close this issue as indicated by the reference here: https://github.com/fubarhouse/pygmy-go/issues/345#ref-pullrequest-1043152302.
I've gone and verified the entire process given I've heard a lot of complaints about v2 (not in pygmy, but many other places and people) and the fact that I don't use Docker Desktop on my daily driver. I'll leave this here for referencing later.
Typical resolution I've seen is to update the docker-compose.yml
file getting updated for compatability.
$ docker version
Client:
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:55:20 2021
OS/Arch: darwin/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:31 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
V2 disabled
Enable v2
Once applied and restarted, start pygmy
Start one or more projects
Proof of project 1 resolving correctly
Proof of project 2 resolving correctly
Retrospectively, proof of V2 being enabled
It may be related to how people are using pygmy with the ssh agent. So, I've done some extra testing and opened this one: https://github.com/docker/compose/issues/8874
Describe the bug Current versions of Docker Desktop ship with Use Docker Compose V2 enabled in Preferences. This setting is not supported by pygmy-go.
Suggest adding it to the Troubleshooting page until Docker Compose V2 support is added in pygmy-go.
To Reproduce Steps to reproduce the behavior:
pgymy-go up
docker-compose up -d
Expected behavior Pygmy starts a reverse-proxy, dns forwarder, ssh-agent and mail capture.
Docker Compose then starts, by using the services including the ssh-agent forwarding.
Screenshots
Output
Additional context Add any other context about the problem here.
Exported configuration
Run
pygmy export --output output.yml
and print the contents fromoutput.yml
below: