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

Cannot start mariadb because mysql is always created and sarted #3338

Closed
realtebo opened this issue Dec 30, 2022 · 4 comments
Closed

Cannot start mariadb because mysql is always created and sarted #3338

realtebo opened this issue Dec 30, 2022 · 4 comments

Comments

@realtebo
Copy link

Description:

when using this command

docker-compose up -d nginx mariadb phpmyadmin redis workspace 

I got this

- Container laradock-mysql-1             Started                                                                                                                                                                                16.4s
 - Container laradock-redis-1             Started                                                                                                                                                                                16.2s 
 - Container laradock-mariadb-1           Starting                                                                                                                                                                               18.8s
 - Container laradock-docker-in-docker-1  Running                                                                                                                                                                                 0.0s 
 - Container laradock-workspace-1         Started                                                                                                                                                                                16.9s
 - Container laradock-phpmyadmin-1        Started                                                                                                                                                                                17.4s 
 - Container laradock-php-fpm-1           Started                                                                                                                                                                                15.1s
 - Container laradock-nginx-1             Started                                                                                                                                                                                15.2s 
Error response from daemon: Ports are not available: exposing port TCP 0.0.0.0:3306 -> 0.0.0.0:0: listen tcp 0.0.0.0:3306: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted.

Expected Behavior:

If we start mariadb, mysql MUST NOT be used

Context information:

Output of git rev-parse HEAD

6c8cb6dd85eb1fcad6f7dce3e9d6c6a29c6e3ed8

Output of docker version

Client:
 Cloud integration: v1.0.29
 Version:           20.10.20
 API version:       1.41
 Go version:        go1.18.7
 Git commit:        9fdeb9c
 Built:             Tue Oct 18 18:28:44 2022
 OS/Arch:           windows/amd64
 Context:           default
 Experimental:      true

Server: Docker Desktop 4.13.1 (90346)
 Engine:
  Version:          20.10.20
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.18.7
  Git commit:       03df974
  Built:            Tue Oct 18 18:18:35 2022
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.6.8
  GitCommit:        9cd3357b7fd7218e4aec3eae239db1f68a5a6ec6
 runc:
  Version:          1.1.4
  GitCommit:        v1.1.4-0-g5fd4c4d
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Output of docker-compose version

Docker Compose version v2.12.1

System info: Mac, Windows or Linux. Include which disto/version

Windows 11

Steps to reproduce the issue:

  1. Clone laradock into a pre-existent laravel 8 project
  2. execute docker-compose up -d nginx mariadb phpmyadmin redis workspace
  3. check that mysql is always created so no way to have mariadb running because of exposing port conflict

Stacktrace & Additional info:

no more info

@realtebo
Copy link
Author

Please, document that when using phpmyadmin you MUST set in the .env this

PMA_DB_ENGINE=mariadb

to avoid this problem.

So no bug, but please, add 2-3 lines of doc about when not using mysql

@stale
Copy link

stale bot commented Apr 2, 2023

Hi 👋 this issue has been automatically marked as stale 📌 because it has not had recent activity 😴. It will be closed if no further activity occurs. Thank you for your contributions ❤️.

@stale stale bot added the Stale label Apr 2, 2023
@realtebo
Copy link
Author

realtebo commented Apr 2, 2023

I would like a reply from the team about doc proposal

@stale
Copy link

stale bot commented May 21, 2023

Hi again 👋 we would like to inform you that this issue has been automatically closed 🔒 because it had not recent activity during the stale period. We really really appreciate your contributions, and looking forward for more in the future 🎈.

@stale stale bot closed this as completed May 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant