Fix strapi network mismatch issues in Docker instructions #2578
Conversation
This file contains hidden or 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
Corrected strapi network mismatch issues. In docker compose everywhere "strapi" as network has been used but in the last segment where network is explicitly is defined it is written "Strapi" due to which while running docker compose up -d it terminates old container and restricts new container due to network mismatch and then i had to manually delete old container and run new container with new network name.
|
|
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
pwizla
approved these changes
Jul 15, 2025
There was a problem hiding this comment.
Thanks, @Tasleem222!
The PR is now approved, merged, should be live on docs.strapi.io in a few minutes, and will be mentioned in the next weekly snapshot release.
pwizla
changed the title
pwizla
pushed a commit
that referenced
this pull request
Jul 15, 2025
Corrected strapi network mismatch issues. In docker compose everywhere "strapi" as network has been used but in the last segment where network is explicitly is defined it is written "Strapi" due to which while running docker compose up -d it terminates old container and restricts new container due to network mismatch and then i had to manually delete old container and run new container with new network name.
pwizla
added a commit
that referenced
this pull request
Jul 15, 2025
Corrected strapi network mismatch issues. In docker compose everywhere "strapi" as network has been used but in the last segment where network is explicitly is defined it is written "Strapi" due to which while running docker compose up -d it terminates old container and restricts new container due to network mismatch and then i had to manually delete old container and run new container with new network name. Co-authored-by: Tasleem222 <[email protected]>
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.
Corrected strapi network mismatch issues. In docker compose everywhere "strapi" as network has been used but in the last segment where network is explicitly is defined it is written "Strapi" due to which while running docker compose up -d it terminates old container and restricts new container due to network mismatch and then i had to manually delete old container and run new container with new network name.
What does it do?
Describe the technical changes you did.
Why is it needed?
Describe the issue you are solving.
Related issue(s)/PR(s)
Let us know if this is related to any issue/pull request