-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bug] Docker Desktop default Preferences to Use Docker Compose V2 breaks pygmy-go #345
Comments
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 Individual projects which utilize
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: #345 (reference). |
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
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. |
* Add ssh-agent no such service troubleshooting docs fixes #345 fixes pygmystack/pygmy-legacy#60 * Remove whitespace from eol in troubleshooting docs * Update docs/troubleshooting.md Make it obvious the content is for Docker Desktop v2 users specifically. Co-authored-by: Karl Hepworth <karl.hepworth@gmail.com> Co-authored-by: Karl Hepworth <karl.hepworth@gmail.com>
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:The text was updated successfully, but these errors were encountered: