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

Custom Container Namespaces #2548

Closed
prezire opened this issue Apr 6, 2020 · 1 comment
Closed

Custom Container Namespaces #2548

prezire opened this issue Apr 6, 2020 · 1 comment

Comments

@prezire
Copy link

prezire commented Apr 6, 2020

Info:
Docker version ($ docker --version): Docker version 19.03.5, build 633a0ea
Laradock commit ($ git rev-parse HEAD): bcae87480d6856e478d08b8e82acce648e6a3275
System info (Mac)

Issue:
MySQL isn't running, with error logs:

mysql_1                | 2020-04-06 13:30:36+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.0.19-1debian9 started.
mysql_1                | 2020-04-06 13:30:36+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
mysql_1                | 2020-04-06 13:30:37+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.0.19-1debian9 started.
mysql_1                | 2020-04-06T13:30:37.469389Z 0 [Warning] [MY-011070] [Server] 'Disabling symbolic links using --skip-symbolic-links (or equivalent) is the default. Consider not using this option as it' is deprecated and will be removed in a future release.
mysql_1                | 2020-04-06T13:30:37.469449Z 0 [Warning] [MY-010915] [Server] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
mysql_1                | 2020-04-06T13:30:37.470855Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.19) starting as process 1
mysql_1                | 2020-04-06T13:30:37.474197Z 0 [Warning] [MY-013242] [Server] --character-set-server: 'utf8' is currently an alias for the character set UTF8MB3, but will be an alias for UTF8MB4 in a future release. Please consider using UTF8MB4 in order to be unambiguous.
mysql_1                | 2020-04-06T13:30:37.501741Z 1 [System] [MY-011012] [Server] Starting upgrade of data directory.
mysql_1                | 2020-04-06T13:30:38.259206Z 1 [ERROR] [MY-012526] [InnoDB] Upgrade after a crash is not supported. This redo log was created with MySQL 5.7.29. Please follow the instructions at http://dev.mysql.com/doc/refman/8.0/en/upgrading.html
mysql_1                | 2020-04-06T13:30:38.260003Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Generic error.
mysql_1                | 2020-04-06T13:30:38.671119Z 1 [ERROR] [MY-011013] [Server] Failed to initialize DD Storage Engine.
mysql_1                | 2020-04-06T13:30:38.674515Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
mysql_1                | 2020-04-06T13:30:38.675015Z 0 [ERROR] [MY-010119] [Server] Aborting
mysql_1                | 2020-04-06T13:30:38.677674Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.19)  MySQL Community Server - GPL.
laradock_{my_project_name_here}_mysql_1 exited with code 1

Expected behavior:
Everything should just run normally like docker-compose up -d nginx mysql redis php-worker laravel-horizon. All containers are running fine including workspace. Only MySQL contains errors.

Reproduce:
I changed the following in my .env:
COMPOSE_PROJECT_NAME=laradock_{my_project_name_here}

Notes:

  1. I've set the project name as a variable in this ticket for privacy.
  2. The reason for having a different namespace was due to multiple, unrelated projects from other teams are using LaraDock. With this, containers such as MySQL with default laradock_mysql_1 container name collides when another LaraDock from another project is also run at the same time.
  3. So the goal for each project is to have namespaces to each of their .env files such as:
    a. COMPOSE_PROJECT_NAME=laradock_{my_project_name_here_1}
    b. COMPOSE_PROJECT_NAME=laradock_{my_project_name_here_2}
@prezire
Copy link
Author

prezire commented Apr 6, 2020

NVM. Just had to delete MySQL's data folder.

@prezire prezire closed this as completed Apr 6, 2020
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