-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
allowing docker container to access service on host #2895
Conversation
docker/docker-compose-base.yml
Outdated
@@ -46,7 +46,7 @@ services: | |||
ports: | |||
- ${MYSQL_PORT}:3306 | |||
volumes: | |||
- mysql_data:/var/lib/mysql | |||
- ./mysql_data:/var/lib/mysql |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
mysql_data
is a volume defined later in this yaml. It's mounted from a docker managed directory.
In rare case if you want to mount from some specific host path, change the volume definion there for yourself.
Revert this chagne please.
@@ -29,3 +29,5 @@ services: | |||
networks: | |||
- ragflow | |||
restart: always | |||
extra_hosts: | |||
- "host.docker.internal:host-gateway" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
I reverted the change of |
### What problem does this PR solve? 1. services running (e.g., ollama) running on the host could not be accessed from docker containers ### Type of change - [x] Bug Fix (non-breaking change which fixes an issue) --------- Co-authored-by: Zhichang Yu <[email protected]>
What problem does this PR solve?
making mysql container unable to start, 44a9152 fixes it.
Type of change