-
Notifications
You must be signed in to change notification settings - Fork 51
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
listen tcp 0.0.0.0:3306: bind: address already in use #9
Comments
@resurtm From what I've understood you've already a MySQL Server running on your Debian system. In docker-compose.yml the MySQL server in the Docker container also gets mapped to I'd suggest to change that to As a sidenote: |
Hi @schmunk42!
Yes, that's true, but as you can see in my OP I've stopped it at systemd level.
Thanks! Will try this way. |
Also wouldn't it be logical to change default MySQL port exposed from the Docker container to something else (as you suggested me 13306)? I think all the people using this project would definitely have MySQL already installed on their host systems. |
Thanks @schmunk42 for pointing it out! ;-) Works for now. |
@resurtm Glad it worked! There are several ways to do this and it depends on personal preference. As an example, if you're running a standalone server you do not have already, mapping the same port is usually the first example. For local development we were using "random" port mapping for a long time also in development, therefore we created make targets to overcome the fiddling in But for testing, especially running multiple stacks in parallel you have to remove the fixed ports at all. Otherwise there'd be conflict when running on the same host. Regards. |
Hello @mikehaertl!
First of all thank you for this project. 😀
I'm not very experienced with Docker, but here's my issue. I have just followed the README. Here's what I had so far:
And here's the additional details (if that would help you):
Cheers,
@resurtm
The text was updated successfully, but these errors were encountered: