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

docs: Connecting to local database when using Superset docker image #22165

Closed
wants to merge 1 commit into from
Closed

Conversation

rukshn
Copy link
Contributor

@rukshn rukshn commented Nov 18, 2022

SUMMARY

When using superset docker image, connecting to a local database using 127.0.0.1 or localhost as the database hose does not work and throws the following error. https://docs.sqlalchemy.org/en/14/errors.html#error-e3q8

The correct host address should be 172.18.0.1 instead of localhost or 127.0.0.1 as written in the superset documentation on this page - https://superset.apache.org/docs/installation/installing-superset-using-docker-compose#5-connecting-superset-to-your-local-database-instance

When using superset docker image, connecting to a local database using `127.0.0.1` or `localhost` does not work and require to use `172.18.0.1` instead as written in the superset documentation on this page - https://superset.apache.org/docs/installation/installing-superset-using-docker-compose#5-connecting-superset-to-your-local-database-instance
Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

Congrats on making your first PR and thank you for contributing to Superset! 🎉 ❤️
We hope to see you in our Slack community too!

@EugeneTorap
Copy link
Contributor

@rusackas ^^

@rukshn rukshn closed this by deleting the head repository Mar 13, 2023
@rusackas
Copy link
Member

rusackas commented Apr 6, 2023

Bummed that the head repo got deleted before we could merge this, but I added it to our documentation task board (bugherd) and hopefully we can tackle this soon :)

@rukshn
Copy link
Contributor Author

rukshn commented Apr 8, 2023

@rusackas shall I make a new PR?

@rusackas
Copy link
Member

@rukshn sure, that'd be great!

@sfirke sfirke mentioned this pull request Oct 2, 2023
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants