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

Add workaround for missing localhost dns on linux #1526

Merged
merged 1 commit into from
Apr 30, 2020

Conversation

smlx
Copy link
Member

@smlx smlx commented Jan 6, 2020

Checklist

  • Affected Issues have been mentioned in the Closing issues section
  • Documentation has been written/updated.
  • Changelog entry has been written

The docker.for.mac.localhost hostname obviously is not available on linux. This PR implements the following workarounds:

  • use bare keycloak service name in docker-compose.yaml where possible
  • make keycloak service name configurable where necessary
  • configure the keycloak service URL in the make up target on linux

Changelog Entry

Improvement - implement configurable keycloak endpoint for linux lagoon development

Closing issues

n/a

@tobybellwood tobybellwood added the 6-images-testing Base Images & Testing subsystem label Jan 6, 2020
@smlx smlx mentioned this pull request Jan 13, 2020
3 tasks
@smlx smlx requested a review from Schnitzel January 20, 2020 06:29
@smlx smlx mentioned this pull request Jan 22, 2020
3 tasks
@tobybellwood
Copy link
Member

Can someone else test this on a mac setup to ensure that the KEYCLOAK_URL isn't being set?

@Schnitzel
Copy link
Contributor

moby/moby#40007 has been merged, but looks like 20.03.0 is not out yet.
@smlx can you check if we would still need this when docker 20.03.0 is out?

vincenzodnp added a commit that referenced this pull request Apr 22, 2020
Upgraded opendistro_security plugin to 1.6.0
Solves #1571: cluster.routing.allocation.disk.threshold_enabled
Add workaround for missing localhost dns on linux PR #1526
@smlx
Copy link
Member Author

smlx commented Apr 24, 2020

There are several issues here.

So I guess once a 20.x docker is released we should be able to avoid this workaround 🎉

vincenzodnp added a commit that referenced this pull request Apr 29, 2020
@smlx
Copy link
Member Author

smlx commented Apr 30, 2020

@Schnitzel I've been dealing with this issue in local development and it's a pain to cherry-pick this patch around between branches. I think maybe it should be merged because:

If/when a better alternative becomes available in upstream docker we can use it. What do you think?

@Schnitzel
Copy link
Contributor

I've been dealing with this issue in local development and it's a pain to cherry-pick this patch around between branches. I think maybe it should be merged

sounds good, let's to this. Can you fix the conflict? will merge after that.

* use bare keycloak service name in docker-compose.yaml where possible
* make keycloak service name configurable where necessary
* configure the keycloak service URL in the `make up` target on linux
@smlx
Copy link
Member Author

smlx commented Apr 30, 2020

Rebased on master and resolved conflicts, just waiting on CI.

@Schnitzel Schnitzel merged commit 0d78879 into master Apr 30, 2020
@smlx smlx deleted the linux-dns-workaround branch May 5, 2020 14:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
6-images-testing Base Images & Testing subsystem
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants