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

ops: get keycloak and server to communicate within docker compose #1474

Closed
cdxker opened this issue May 17, 2024 · 2 comments · Fixed by #1517
Closed

ops: get keycloak and server to communicate within docker compose #1474

cdxker opened this issue May 17, 2024 · 2 comments · Fixed by #1517
Assignees
Labels
bug Something isn't working high priority ops Anything with "auto actions"

Comments

@cdxker
Copy link
Member

cdxker commented May 17, 2024

Community channels

Matrix is preferred. Reach out on discord or Matrix for further assistance.

@cdxker
Copy link
Member Author

cdxker commented May 17, 2024

The issue seems to be with the docker network inside of itself.

@jooni22
Copy link
Contributor

jooni22 commented May 24, 2024

This is a common problem in communicating with the API on docker-compose, it can be solved by implementing CORS support in the application code, there are several solutions in several popular languages, you can follow them and add support in the code. You can read more under this post:
https://maximillianxavier.medium.com/solving-cors-problem-on-local-development-with-docker-4d4a25cd8cfe

(NOTE! this solution works only on Linux systems)
Another solution is to move the API Server outside the internal docker network and use the attribute:
network_mode: "host"
instead of:
networks:
- app-network
In order for the app to work correctly with the current logic, the "ingestion-worker" and "file-worker" services must also be moved to the "host" network.

@cdxker cdxker closed this as completed May 24, 2024
@cdxker cdxker linked a pull request May 24, 2024 that will close this issue
@cdxker cdxker reopened this May 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working high priority ops Anything with "auto actions"
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants