Skip to content
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

Remove deprecated gateway external name #186

Merged
merged 2 commits into from
Oct 20, 2021

Conversation

DonRichards
Copy link
Member

@DonRichards DonRichards commented Oct 11, 2021

Fix warnings

Screen Shot 2021-10-11 at 11 14 22 AM

@DonRichards DonRichards requested review from nigelgbanks and a team October 11, 2021 17:41
@seth-shaw-unlv
Copy link

Can we get testing instructions to reproduce the issue and then demonstrate the fix? Thanks.

@DonRichards
Copy link
Member Author

DonRichards commented Oct 14, 2021

@seth-shaw-unlv Just run make demo or some anything to bring it up. The warning should come up. I got this warning on both Linux and MAC. The error is part of the fresh build process. Perhaps run make clean first.

@DonRichards
Copy link
Member Author

Just noticed another ticket has the warning within the output example. Although his ticket is referencing a composer version issue, it does show the warning messages I posted here. Not completely related but it shows the issue arises when the build process is fired (make local|demo).

#184

@nigelgbanks
Copy link
Contributor

Looks like the format has changed so we should, set external: true like so:

gateway:
  external: true
  name: gateway

Our current method was deprecated in version: "3.5". In all our docker-compose files we have version: "3.7"

It looks like external: true must be specified for it to work as it was previously.

@nigelgbanks
Copy link
Contributor

nigelgbanks commented Oct 17, 2021

Looks like we don't need to specify name either if it matches the same as the network configuration.

docker network ls                          Sun 17 Oct 2021 12:54:49 UTC
NETWORK ID     NAME              DRIVER    SCOPE
eb0abd23fac3   bridge            bridge    local
1df64990806d   host              host      local
4943545796cd   isle-buildkit     bridge    local
225f8df1f00d   isle-dc_default   bridge    local
85f08ed21a62   isle-dc_gateway   bridge    local
e540e0060f15   none              null      local

So the following would be fine.

gateway:
  external: true

Here we can see that Alpaca is only on the default internal network as is expected and Drupal is on both.

docker inspect isle-dc_alpaca_1 | jq '.[].NetworkSettings.Networks | keys[]'
"isle-dc_default"
docker inspect isle-dc_drupal_1 | jq '.[].NetworkSettings.Networks | keys[]'
"isle-dc_default"
"isle-dc_gateway

Copy link
Contributor

@nigelgbanks nigelgbanks left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've made the changes I've recommend and tested it locally see the previous comment for the output.

@nigelgbanks
Copy link
Contributor

@DonRichards if you're happy with my changes I'll go ahead and merge it.

@DonRichards DonRichards merged commit 9d0c28f into development Oct 20, 2021
@DonRichards DonRichards deleted the fix-network-external-warning branch October 20, 2021 13:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants