Fix network issues when running composer in ddev #145
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
greggmarshall
added a commit
to greggmarshall/Labdoo-3.0
that referenced
this pull request
Apr 17, 2022
…tpod See shaal/ddev-gitpod#145 for the information about why.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Temporary fix for network issues when running composer inside ddev container (in Gitpod)
Summary -
Since Gitpod removed slirp4netns as part of performance improvements,
MTU value should be aligned to the one in gitpod.io
Gitpod fixed it for docker - gitpod-io/gitpod#9356
and for docker-compose - gitpod-samples/template-docker-compose#4
ddev doesn't use Gitpod's custom docker-compose binary. Instead, ddev uses
its own docker-compose binary at /home/gitpod/.ddev/bin/docker-compose
ddev issue [WIP] - ddev/ddev#3766
Align the MTU value to the one that is set in Gitpod (1440)